Crystal and Reporting Services FAQ - Part 2
We have two IIS application â€˜Reportsâ€™ and â€˜Reportserverâ€™ what do they do ?
Can you explain Report definition language (RDL) file in reporting services?
How can we consume reports in ASP.NET?
Can you explain the difference between private and shared data sources?
How does reports caching in reporting services work ?
How does reports caching in reporting services work ?
What are the major differences between Crystal and SQL reporting services?
This FAQ will give you a quick start for two giant reports on Crystal and Reporting Services.
Get here Crystal and Reporting Services Interview Questions - Part 1
When you install reporting services there are two virtual directories created as shown in the figure below.
Figure : - IIS Applications for reports
The â€˜Reportsâ€™ virtual directory is like an admin. If you browse to http://yourpcname/reports/home.aspx page you can view, edit properties and display reports. We have numbered the below figure. 1 Ã We can browse reports and see the output of reports. 2 Ã We can upload a RDL file directly in the reportâ€™s database. 3 Ã Using the report builder link we build new reports. 4 Ã Using the properties we can do role assignment. 5 Ã Using subscription link we can add new outputs (FTP, Folder etc) to subscribe to the reports. 6 Ã Site settings help us to decide how many numbers of snapshots we want in the history, report time out execution, report execution logging, scheduling, manage jobs and security settings.
Figure :- Reports Admin
The second virtual directory is the â€˜ReportServerâ€™ this helps us to use browse reports and use the same in ASP.NET code using URL methodology , try browsing to http://yourpcname/reportserver/ you can easily figure out what this virtual directory is all about.
RDL is an XML description of a report in reporting services. So basically the RDL file has the XML grammar which describes a reporting services report. Below figure â€˜Snip of RDL fileâ€™ shows a simple snippet of a RDL file.
Figure : - Snip of RDL file
What is the basic process of making a report in reporting services?
Here are the basic steps which will help you in creating reports in reporting services:-
â€¢ Open Visual studio 2005 Ã File Ã New project Ã Select â€˜Business Intelligence Reportsâ€™ Ã Select Report Server project.
â€¢ When the project is created in the solution explorer you will see two folder â€˜Shared data resourcesâ€™ ( we will come to data sources in the coming questions) and â€˜Reportsâ€™. Right click the â€˜Reportsâ€™ folder and click add new reports.
â€¢ You need to give credentials in the wizard. Once done it pops up a query builder. Specify the report query in the query builder and go next.
â€¢ Wizard then helps you to select the report type and some other features. Next , next and you should see a RDL file in your â€˜Reportsâ€™ folder.
â€¢ Click on the view menu and select tool box and you should be able to design the report.
â€¢ Till now we are only in the design mode of report. As said previously all reports meta-data are stored in SQL Server database â€˜ReportServerâ€™. In order that the reportâ€™s meta-data gets saved in database we need to publish the report.
â€¢ To publish the report we need to specify the IIS report path. So right click on the report project, select properties and specify the â€˜TargetServerURLâ€™ property.
Figure :- TargetServerURL property
â€¢ Once we have specified the â€˜TargetServerURLâ€™ property we need to deploy the project. So right click on project and click â€˜Deployâ€™
Figure : - Deploying reports
â€¢ You can now view your report using http://localhost/Reports/Pages/Folder.aspx URL.
There are three famous ways of calling reporting services report in ASP.NET:-
â€¢ Using URL way to access reports.
â€¢ Using reporting web service to programmatically access reports.
â€¢ Using report viewer control.
This is the most basic way of accessing reports. We specify the URL as shown below which then displays the report on the browser. Below is a basic format of how to display a report using the URL methodology. 1 Ã This is the IIS report application. 2 Ã This is the project name or the project folder in which the report resides. 3 Ã This is the report name. 4 Ã This is the command to the reporting service of what to do. In this case we are saying render the report.
Figure : - Basic URL
If we want to get the report in PDF format we need to use the â€˜Formatâ€™ parameter.
Figure : - Generate the report in PDF format
If we want to pass parameters to the report we can do something as shown in the figure â€˜Pass parameters to the reportâ€™. In this scenario we have passed the â€˜Categoryâ€™ parameter.
Figure : - Pass parameters to the report
Consuming reporting services web service
If you look at the architecture of reporting service all reports are exposed through XML i.e. Web services.You can see the web service using this URL http://localhost/ReportServer/ReportService2005.asmx. In localhost you need to put the server name or IP address. So below are the steps to display reports using web service.
Step 1 Ã First add the web service using http://localhost/ReportServer/ReportService2005.asmx in your ASP.NET project.
Step 2 Ã We need to consume the web service and use it. Below is the code snippet which shows how the reporting service object is used. 1 Ã You can see the web service references to â€˜reportservice2005.asmxâ€™. 2 Ã We have the named the web service as â€˜Localhostâ€™, so you can see we have imported the web service. 3 Ã We need to create object of â€˜ReportingService2005â€™ class. 4 Ã We need to set the credentials of the reporting object. 5 Ã In this we will display which reports are present in the reporting server database. So we use the â€˜ListChildrenâ€™ method to get the reports from the web service and then loop to display the same. 6 Ã This sample code should display the reports present in the reporting service.
Figure : - Display reports in reporting server
The above example is a sample of how to use the reporting web service. If you want to get how many input parameters the report has we need to use â€˜GetReportParametersâ€™ method, if we want to display the report we use the â€˜Renderâ€™ function. There are many other function and methods which we have not discussed to keep the chapter simple and to the point. Please experiment around the reporting web service object for new methods and functions.
ASP.NET 2.0 comes with crystal report viewer control. You can drag and drop the control on the ASPX page and set the properties. Below figure shows how the â€˜ReportviewerControlâ€™ looks like and how we can set the properties to view the report.
Figure :- ReportViewerControl in action
Private data source is used by single report only while shared data sources are shared between reports. As a practice it is good to have shared data source so if you want to change anything you need to change only on one data source.
As said previously reporting services has two main databases â€˜ReportServerâ€™ and â€˜ReportServerTempDBâ€™. Below figure â€˜Reporting Services Cachingâ€™ shows how caching works in reporting services. Client first sends a request to the reporting service for report. Reporting processor gets data from the database and the report format from the â€˜reportserverâ€™ database. Both these elements are then used to create â€˜Intermediate report formatâ€™. This intermediate format is saved in â€˜ReportServerTempDBâ€™. This intermediate format is for a particular user and for a session. So if the user generates the same report he will get a cached version. If the report is having parameters then there are different cached versions of report for every parameter combination. Cached versions expire after particular schedule, when reports are modified, deleted or redeployed.
Figure : - Reporting services Caching
In order to set the caching properties browse to a particular report using http://localhost/reports/ Ã click on properties Ã and go to execution tab. Below figure â€˜Caching optionsâ€™ shows different conditions on which you can define caching strategy.
Figure :- Caching strategy
Ease of hosting reports: - Using the URL technology in RS we can host reports more easily than in crystal report where we need to make a UI for the same.
Supporting platforms: - Crystal can run on windows, IBM and sun while RS (reporting services) can run only on windows environment.
Client tools: - In reporting services we have Business intelligence ( BI ) and development studio while in crystal its Report designer.
Caching: - This achieved in crystal by using cache server while in reporting services itâ€™s stored as snapshots in Reportserver database.
Export formats:- In crystal we have HTML,PDF,Excel,XML,Word , PDF , RTF , CSV, text files while in SQL Server 2005 we have all the formats above it also gives capability to extend custom reporting formats.
Data sources:- Crystal support more data sources while RS only supports Microsoft and oracle data sources. Crystal supports ADO, COM, Database excel Access, Exchange, NT, Xbase, JDBC, File system and Paradox. RS supports only SQL Server, Oracle, ODBC, OLEDB and you can also extend additional data sources which does not exists in crystal reports.
Version issues: - One of the main issues faced in crystal is it have different versions which makes it difficult to use, while RS comes with SQL Server minimizing the version issue.
Web server support: - Crystal can run on IIS 5/6, Apache, lotus etc while RS works only with IIS 5.0 and above.