I'm looking for a ASP.NET report generation engine, with this feature: interactivity, this means the user must be able to move from more general data to more detailed data (clicking on report elements, like rows or columns).
Thanks
It looks like you want a drill down interactive reporting engine? SQL Server Analysis Services (SSAS) in combination with SQL Server Reporting Services (SSRS) provides the features you need; you can drill down through your data in a very dynamic way, and it works very well.
And you can deploy that to ASP.NET.
HTH.
SQL Server Reporing services does provide the functionality you are looking for but there are security issues if you try to put it on an internet facing server.
SSRS was designed to be an intranet reporting tool. This paragraph comes from the first link below:
"Although SQL Server Reporting Services is not expressly designed for extranet or Internet report deployment scenarios, you can successfully put Reporting Services on an Internet-facing Web server to distribute general information to the public at large or private corporate data to authorized and authenticated users."
Have a read of the following:
http://msdn.microsoft.com/en-us/library/ms159272.aspx
Internet Facing SSRS Report
http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx
Related
I have developed web application for restaurant. Its Front office is developed for iPad and back office maintain .net web application .
SQL Server 2008 is used as database.
I want to make offline application for Front office which can be used when unable to connect network / DB Server using iPad.
Master table's data cannot be Modified but, there should be latest data of master table to
transaction in other pages.
whenever system is connected to internet all offline transaction should synchronize with online data
It will be better if can suggest me solution without installing sql at client
I have think to use save data xml/json files as per table structure but its not preferable with large numbers of tables and clients and also security issue is there
Please guide me on this. Any help would be appreciated
Thanks in advance
Just to be sure: Your frontend is developed using HTML-Technologie?
You could use HTML5 Local Storage and/or offline caching with a manifest.
I think you have to put your data there by hand, but you could write a function for this...
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!!
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'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?
we need reports in our web application and there is the free ReportViewer Control from microsoft (normally used, to display reports from the reporting services). I like the fact, that the Report Format (.RDL-Format) from the ReportViewer is a documented XML-Format. But the functionality is somewhat limited, when the ReportViewer is used without the ReportingServices.
Is there a good replacement, which is based or compatible with the .RDL-Format?
The first Reports are build in the application, but later, the customer should make his reports by himself.
The Application is a ASP.NET Web-Application
This depend on your requirements. I am not clear what your requirements are.
Is your application a web application or a desktop application?
If your application is a web application then you can use any other reporting service. I like i-net Clear Reports. There is also a free and fully functional GUI report designer that is easy to use. Your customer can create your own reports.
If you have a desktop application then you are limit to the language of your application.
You should also think about the platforms. The reporting services are limited to windows and a SQL Server is needed. Does all your customer have a SQL Server?
Sorry, I have forgotten to write, that the application is a asp.net web application