I'm working on a solution to create reports in a web application but don't have the budget or personnel to manage a SQL Server Reporting Services install. What alternatives do I have, given these constraints?
I'm using ASP.NET 3.5 on SQL Server 2005.
You could use SSRS but in local mode not server mode. From my understanding you don't need SSRS when reports are rendered with this method. You will also be required to write more code to support the reports.
Other options then include looking at other reporting packages out there. Crystal Reports is one possibility but if you can't manage SSRS, I'm guessing CR would not be a possibility.
Anyways here's some links for SSRS in local mode:
http://www.vbdotnetheaven.com/UploadFile/justinsaraceno/Main11132006012727AM/Main.aspx
http://aspalliance.com/1318_Using_Local_Microsoft_SQL_Server_Reporting_Services_in_ASPNET
Perhaps you can use Jasper: http://jasperforge.org/
I believe there is a jTDS driver to connect to sql server.
I have no clue if this will work or is supported, just an idea.
HTML is a reporting layer. Do you need another one?
Related
I know PHP and how to use MySQL with it but now I am moving onto ASP but which common database is used with ASP (ie. the equivalent to MySQL)?
Microsoft SQL Server.
This is commonly known as WISA (Windows, IIS, SQL Server, ASP) stack.
It is Sql Server (Express editions are free) but you shouldn't let this be your only deciding factor. Besides, it doesn't really matter. The db is the back end, unseen by your clients, and you can connect to many, many types of DBs from ASP just as well as to Sql Server.
Your main consideration should be features, scalability etc. For the sake of picking up this dev stack quickly I would suggest sticking with MySql for you. That would be one less rather large piece of technology to learn!
Also: Are you moving onto ASP (classic) or ASP.NET? If it is ASP I would recommend that you reconsider and choose a more modern web development methodology such as ASP.NET MVC or Silverlight. I think that you will find ASP.NET MVC to your liking. In some ways it feels like ASP or PHP of old but with much more flexibility.
Usually it's Microsoft SQL Server.
If you want a free alternative you could try with Microsoft SQL Server Express, which is a scaled down version.
Here you can find more informations about the different versions.
MS SQL server is commonly used with ASP (Classic and .NET). There are many different versions of SQL (SQL Express, Standard Edition, Enterprise etc)
I'm working on a project where we will be interacting with the ReportService2010 reporting web service under SQL Server 2008 R2. In the past, I've worked with the ReportService2005.asmx, and my problem here is, I can't find any reasonable examples on how to render a report with this new (2010) reporting web service.
When using the 2005 web service, there was a "Render" method that was provided when creating your proxy with the wsdl.exe utility. Is there an equivalent method (or set of methods), to accomplish the same thing using the ReportService2010 service? Or are there any decent examples of an end-to-end intialization and calling of the new proxy?
Even MSDN doesn't have much information, and in certain parts of the ReportService2010 API docs, there are old snippets of code that were only applicable to the 2005 web service.
UPDATE: A better question might be how have things changed between SSRS 2008 and SSRS 2008 R2 with regard to calling the report service(s) programmatically...I can see that even under SSRS 2008 R2, there still exists a ReportService2005.asmx, as well as a ReportExecution2005.asmx, but there is not a corresponding ReportExecution2010.asmx.
sigh
SOLUTION UPDATE:
After talking to someone at my company, I was informed of the following:
The 2006 web service was introduced to support sharepoint integration in 2008.
The ReportService2010 web service was introduced to merge all the functionality introduced by 2006 with the 2005 web service.
ReportService2005 web service will continue to be used for report execution. I don't know why, but something tells me it has to do with business decisions for backwards compatibility. My coworker said we are intended to continue to use ReportExecution2005 for rendering, and ReportService2010 for all other functionality (querying the SSRS server for reports, params, etc).
Unfortunately all the above information was culled from a variety of links, none of which concisely stated all of the above. It's the kind of thing that you would normally assume a vendor to explain to client developers.
SQL Report Server provides 3 different endpoints.
ReportService2010: Provides the APIs for managing a report server that is configured for either native or SharePoint integrated mode.
ReportExecution2005: Provides the APIs for running and navigating reports.
ReportServiceAuthentication: Provides the APIs for authenticating users against a report server when the SharePoint Web application is configured for Forms Authentication.
Thus, in order to render the report you must use this one ReportExecution2005.
Here it says what I have pasted above: http://www.blograndom.com/blog/2011/03/reportservice2010-asmx-is-not-the-only-end-point/
Here you can find an example (it has some errors though) to get started
http://blogs.msdn.com/b/christophputz/archive/2010/05/07/accessing-ms-reporting-services-with-java.aspx
Good luck!!
I need to develop a dynamic web page retrieve data from a stored procedure on a SQL Server.
Considering the licensing issue, development resources, security and maintainability, can someone suggest a suitable platform for this project?
I have a Ubuntu server running Drupal and also a Windows Server 2003 running SQL Server 2000 and IIS for FTP server only.
Is ASP.NET and Reporting Service the natural choice? What are my other options? Ruby On Rails? Since the SQL Server on the server is mission critical and I don't feel very comfortable asking anymore from it.
SSRS is very good for the price; though in SQL 2000 its a bit limited - especially for charting. If you have a small budget you could write nice looking reports using stored procedures and something like telerik reporting if you want to do a bit more of the work on the web server. There is a trial version you could use for a quick prototype to see how it fits in; but it works very nicely with asp.net development and is nicely integrated with Visual Studio.
Client has a bunch of Access databases and associated reports.
He wants to make the reports available (live, not snapshots) via a secure extranet.
He's willing to recreate the reports using a proprietary GUI if necessary, but ideally would like a solution that exports his reports "as is" to the web.
Had a look at Caspio Bridge. It's pretty slick but doesn't appear to offer grouping and summing (key requirement) without a nasty Javascript hack - seems like a rather glaring omission to me!
Any suggestions?
I'm an ASP.NET developer so if there's coding involved, an ASP.NET based solution would be preferred.
You can try Access Reporter.
http://www.ssw.com.au/ssw/AccessReporter/Default.aspx
You might like to consider Access 2010, point 3 of the linked document says:
Access your application, data, or
forms from virtually anywhere.
Extend your database to the Web so
that users without an Access client
can open Web forms and reports via a
browser and changes are automatically
synchronized.1 Or work on your Web
database offline, make your design and
data changes, and then sync them to
Microsoft SharePoint Server 2010 when
you’re reconnected. With Access 2010
and SharePoint Server 2010, your data
can be protected centrally to meet
data compliance, backup, and audit
requirements, providing you with
increased accessibility and
manageability.
-- http://www.microsoft.com/office/2010/en/access/default.aspx
SQL Server Express edition is free. It includes Reporting Services
http://www.microsoft.com/Sqlserver/2005/en/us/express.aspx
You can connect to the MS Access database (or any other database that you have OLEDB or ODBC connectivity for)
For your existing reports, here is a link on how to migrate just the reports to SQL Server (leave data in MS Access)
http://technet.microsoft.com/en-us/library/cc966391.aspx
Actually, the suggestion being given here is to move your back and data up to SQL server , but keep your front end application part as is in Access.
So the suggestion isn’t to move your application to SQL server. The suggestion here is to move only the data part of your application to SQL server but continue to use the desktop access application.
So, you link your tables to sql server, and continue to use the access application.
What this means that is you can use SQL server reporting services, or some other web based interface that pulls the data from SQL server. So your access application will be directly updating the data on that SQL server.
This setup works well since you not tying to shuttle data between two separate systems. I know a number of companies that successfully migrated their backend data to SQL server for this very purpose of allowing the Executives and the company Managers to view reports on a web based system.
However, they did not have to throw out or lose the investment and time they spent building the access application part.
I am using a ASP.NET with c# website and MSSQL Server 2005 DB.
Will be hosting on a shared hosting provider..so i cannot install any runtimes/other software or services. i dont have MSRS (Microsot reporting services) or others as well.
I need to find some good reporting alternatives besides Crystal Reports and other heavily paid services.
I need to be able to generate reports with grouping , query based, cumulative, formula based, sub reports within one report, simple graphs and charts, etc
Please help me with this issue.
(i tried LogiReports from http://www.freereporting.com/product/index.html)
but it is difficult to use.
Thanks and Regards
prad
Have you considered Telerik Reports? It does not need any special software installed on your deployment servers. The reports that you create are in a dll that deploy along with your application. It is not free, but it is still very nice.