 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Services / Reporting Services / November 2006Reporting Services 2005 newbie questions
Hi all, I am a newbie to reporting services and am assigned the task of building an architecture for hosting reports for different departments in the organization. I am setting up a prototype and have a few questions: Environment: SQL Server 2005, VS 2005. 1. I understand that I can use either the ReportViewer control or the Reporting Services web service to create reports. Which is recommended and why? 2. Which is the best way to render a report? The reports will be consumed from a Java/JSP environment. 3. What is the difference between Local and a Server mode for Reports? 4. How do I make a determination while developing reports whether to use more RDL or to have more logic embedded in the ASP.NET application Thanks, Hello, Any help is really appreciated. Thank you. > Hi all, > [quoted text clipped - 18 lines] > > Thanks, I suggest looking at some links on MS site: http://msdn2.microsoft.com/en-us/library/aa964126.aspx http://msdn2.microsoft.com/en-us/sql/aa336316.aspx First, the control can only be used with a 2.0 framework asp.net website. If that is the case then that is the easiest way to integrate in. Although you say java/jsp which confuses me. asp.net <> jsp. Local mode requires a good bit more work. You provide the tableset for it but you also have to respond to events for subreports and other things like that. It is not as easy as developing server based reports. You also lose out on functionality like caching, subscriptions etc provided by the server. My suggestion is first learn RS. Install the development environment, create some reports and subreports. Try doing some typical things. If the end result is that your app is not an asp.net app they you have to roll your own integration and use either webservices or URL integration.  SignatureBruce Loehle-Conger MVP SQL Server Reporting Services > Hi all, > [quoted text clipped - 18 lines] > > Thanks, Thanks for your suggestions. The reporting project will be .NET based but the Web application that is consuming these reports is a JSP app. Right now I think the best approach is to use URL method of embedding reports and using a IFRAME to render. Is there a better way? I guess I will stick with the Servermode for now for the advantages you mentioned. Here's the environment I have in mind. 1. Create a VS 2005 project a ASP.NET application that has a page for displaying reports. Say Report.aspx 2. Create another project for all the data sources and the report definitions 3. For integration with a JSP app, have the page call the Report.aspx page and send as query string params - the report name, the parameters. 4. The Report.aspx that hosts the ReportViewer control sets the Report path dynamically and renders the report. Will this architecture be scalable? We plan to host hundreds of reports. The other question is to how to use the query parameters from the Report.aspx to create datasources (does this need to be done programmatically)? > I suggest looking at some links on MS site: > http://msdn2.microsoft.com/en-us/library/aa964126.aspx [quoted text clipped - 42 lines] > > > > Thanks, My suggestion is to start off with just a report project. RS comes with its own portal called report manager. There is no reason to have another web page getting in the way. Have your JSP app just assemble the appropriate URL string. Although you could do web services URL string is most likely the best way to go. One other issue. Is this an intranet or internet application? SignatureBruce Loehle-Conger MVP SQL Server Reporting Services > Thanks for your suggestions. > [quoted text clipped - 75 lines] >> > >> > Thanks, Thanks Bruce for your reply. This will be an internet application. Can you please explain how I could use the Report Manager as a substitute for a Report.aspx page? I found out that a datasource can be a stored procedure with params and my initial plan was to use the Report.aspx page to grab the params and send it to the SP. > My suggestion is to start off with just a report project. RS comes with its > own portal called report manager. There is no reason to have another web [quoted text clipped - 89 lines] > >> > > >> > Thanks, As an internet app you will need to do forms based authentication (non-trivial). Be sure to read up on that. You pass parameters to the report via the URL. The report is the one that calls the SP with the params. This will make more sense once you create a report. Note that you can create and test reports without deploying to a server. So you can install the report designer and start working on some reports to learn prior to install and configuring the server. SignatureBruce Loehle-Conger MVP SQL Server Reporting Services > Thanks Bruce for your reply. > [quoted text clipped - 114 lines] >> >> > >> >> > Thanks, |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.