What do you think?
Rate this book
Pro SQL Server 2005 Reporting Services
At its core, the process of designing reports hasn’t changed substantially in the past 15 years.
The report designer lays out report objects, which contain data from a known data source, in
a design application such as Crystal Reports or Microsoft Access. He or she then tests report
execution, verifies the accuracy of the results, and distributes the report to the target audience.
Sure, there are enough differences between design applications to mean that the designer
must become familiar with each particular environment. However, there’s enough crossover
functionality to make this learning curve small. For example, the SUM function is the same in
Crystal Reports as it is in Microsoft Access as it is in Structured Query Language (SQL).
With Microsoft SQL Server 2005 Reporting Services (referred to as SSRS throughout the book),
there is, again, only a marginal difference in the way reports are designed from one graphical
report design application to another. So, if you do have previous reporting experience, your
learning curve for SSRS should be relatively shallow. This is especially true if you come from a
.NET environment, because the report designer application for SSRS is Visual Studio 2005 or
the application included with SQL Server 2005, Business Intelligence Development Studio (BIDS).
Having said all this, several differences set SSRS apart from other reporting solutions:
• It provides a standard reporting platform based on Report Definition Language (RDL),
which is the XML schema that dictates the common structure of all SSRS reports. This
allows for report creation from any third-party application that supports the RDL schema.
• SSRS is an integral part of the SQL Server 2005 release.
• SSRS offers features out of the box that in other products would be expensive additions
to a basic deployment. These features include subscription services, report caching,
report history, and scheduling of report execution.
• SSRS, being a Web-based solution, can be deployed across a variety of platforms.
This book was written in parallel with a real SSRS deployment for a health-care application,
so it covers almost every design and deployment consideration for SSRS, always from the standpoint
of how to get the job done effectively. You’ll find step-by-step guides, practical tips, and
best practices, along with code samples that you’ll be able to modify and use in your own SSRS
applications.
The report designer lays out report objects, which contain data from a known data source, in
a design application such as Crystal Reports or Microsoft Access. He or she then tests report
execution, verifies the accuracy of the results, and distributes the report to the target audience.
Sure, there are enough differences between design applications to mean that the designer
must become familiar with each particular environment. However, there’s enough crossover
functionality to make this learning curve small. For example, the SUM function is the same in
Crystal Reports as it is in Microsoft Access as it is in Structured Query Language (SQL).
With Microsoft SQL Server 2005 Reporting Services (referred to as SSRS throughout the book),
there is, again, only a marginal difference in the way reports are designed from one graphical
report design application to another. So, if you do have previous reporting experience, your
learning curve for SSRS should be relatively shallow. This is especially true if you come from a
.NET environment, because the report designer application for SSRS is Visual Studio 2005 or
the application included with SQL Server 2005, Business Intelligence Development Studio (BIDS).
Having said all this, several differences set SSRS apart from other reporting solutions:
• It provides a standard reporting platform based on Report Definition Language (RDL),
which is the XML schema that dictates the common structure of all SSRS reports. This
allows for report creation from any third-party application that supports the RDL schema.
• SSRS is an integral part of the SQL Server 2005 release.
• SSRS offers features out of the box that in other products would be expensive additions
to a basic deployment. These features include subscription services, report caching,
report history, and scheduling of report execution.
• SSRS, being a Web-based solution, can be deployed across a variety of platforms.
This book was written in parallel with a real SSRS deployment for a health-care application,
so it covers almost every design and deployment consideration for SSRS, always from the standpoint
of how to get the job done effectively. You’ll find step-by-step guides, practical tips, and
best practices, along with code samples that you’ll be able to modify and use in your own SSRS
applications.
First published September 27, 2004
5 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
No one has reviewed this book yet.