By Ben
Reporting Service SP1 for SQL Server 2000 Preview Research
Environment: WinXP, SQL Server 2000 SP
3A
.NET 1.1
Attachment: (download attachment)
Project: Reporting Service Reports Project
SETUP: Reporter Publish Setup
Web: Reporting Service web application
WIN: WIN Application for Reporting Service
Research ideas:
1. Understand the basic concepts of familiar with Reporting Service
2. Install Run Reporting Service
3. Configure the Reporting Service settings
4. Design report
5. Implement .NET program call report
6. Implement Installation Report
Overview
Reporting Service and the familiar crystal report are the same class: Report Tools.
Based on SQL Server 2000, combined with VS.NET powerful designers can easily realize report production
Reporting Service Components:
1. Web Report Manager (http:// localhost / reports)
2. VS.NET Report Designer
3. Report Web Service (http://localhost/reportserver/reportservice.asmx)
4. Reporting Service Web End Point (http: // localhost / reportserver)
The report mainly consists:
Data Source (RDS) Configure database connection strings. It is a standard XML file
Report (RDL) Configuring SQL statements, report styles. It is also a standard XML file
Installation
Demand environment: SQL Server 2000 SP
3A
Settings 1, the web path of the component 4 can be set during the installation process (the default path settings for this study)
Proof
2. Configuration
Go to Web Report Manager (http: // localhost / reports)
A. Manage users
User role point:
Publishers can post reports and linked reports to the report server.
Viewers can view folders, reports, and subscribe reports.
The content administrator can manage the contents of the report server. Includes folders, reports, resources.
My report can publish reports and link reports; manage folders, reports, and resources in the My Reports folder of the user.
User Permission Settings is similar to our familiar SharePoint, you can set the permissions of the report web side site and the permissions of a report.
Different, the Reporting Service Permissions Settings can combine SQL user settings to achieve more specific permission assignments.
The key is that the data source connection of the report should be verified by Windows (the purpose is to bring the web access to the Windows identity to SQL), and cannot be saving SA users.
B. Subscriptions of reports
This is also similar to SharePoint, which can subscribe to some reports. (Specific implementation is slightly in this study)
C. History of the report
You can implement snapshot functions, you can manually create Snapshot, you can also implement unmanned operation - Settings the Snapshot Plan automatically creates snapshot. (Specific implementation is slightly in this study)
D. The "Execution" settings of the report
You can set the data buffer of the report, execution time (timeout). (Sketch of the specific implementation)
In addition, RDS, RDL (data source, report) can be uploaded. Since they are just an XML file, it can be flexible.
Window Service Analysis by ReportingServicesSservice.exe
3. Design report
1) Run vs.net
2) Creating a project ->
3) (At this point, you can see a Reporting Service project template in the list of "Smart Business Projects" from the project template classification, and create a Reporting Service project template and create
Creating a report can be created using the wizard, and the advanced point can also be created manually.
The project will automatically generate two folders: shared data sources, Reports
Here is the main process of manual creation:
A. New data source. Use the right-click to add new items to create a data source in the Folder shared data source. It will automatically generate a RDS file B. New report. Similarly, use the right-click to create a report, it will automatically generate an RDL Document. Here we can design report style like design ASP.NET pages
C. Publish / deploy the web side of the Reporting Service.
First open the project property of the report:
OverWriteDataSources: True | False Whether to overwrite the current RDS data source
TargetFolder: Directory deployed to the Reporting Service's web-side report, such as entering Demoproject, you need to access deployment in http: // localhost / reportServer / Demoproject
TargetServerURL: WEB path deployed to the Reporting Service web site
StartItem: This is running on vs.net, pressing the report boot item for Running report project Project by ctrl f5
4. .NET program call report (see attachment for instance)
Method 1: It is also the simplest call, just open the report of the Reporting Service web-side station with brower.
You can use the URL parameters as the input parameters of the report, and the details, please see the DynamicQuery.rdl of the attachment Web project.
Method 2: By calling the Web Service provided by Reporting Service. It has a number of Web Method for call
5. Publish installation report
After installing the Reporting Service, there will be a RS.exe tool. Path "% systemDrive% / program files / microsoft sql server / 80 / Tools / Binn / RS.exe"
You can take a look at the Help of RS.exe, which supports several specific parameters, using .RSS script implementation to install RDL, RDS to the web end site
A SETUP program has been designed. See annex SETUP directory
to sum up:
Feel
The shortcomings of Reporting Server:
There are still some immature in the Reporting Service report.
Design reports are inconvenient; web-side browsing reports must be printed after exporting; some settings are invalid (this is like setting ASSIE SESSION SESSION Sension time when the time is incomplete);
Complex reports (such as nested subscriptions, such as Supplier.rdl in the attachment).
That is, the Reporting Service is still a comparison of COOL report tools.
It is also the characteristics of some of its characteristics as described above.
