Databases Reference
In-Depth Information
An in-depth discussion of programmatic rendering may be found in Chapter 12
.
Even for the novice
programmer, creating these kinds of solutions is relatively simple and may be accomplished with just a
few lines of program code.
Report Definition Language
Rather than defining a proprietary specification for individual report definitions, our friends at Microsoft
took a very different approach. They chose to publish an extensible and well-documented standard. The
entire set of instructions that define a report are stored in a single XML document using an RDL XML
grammar. If necessary, property values for elements of a report's design could be modified with a text edi-
tor. If someone wanted to build a report design tool, he or she would simply need to output the appropri-
ate XML tags to an RDL file. This also makes it easy and convenient to send the report definition to
someone or to deploy a report to another server.
Deploying Reports
Reports are defined in an RDL file, but the report's definition is stored in the Report Server database
once it has been deployed to the server. Report deployment may be performed in at least three different
ways. In Visual Studio 2005, the project defines a corresponding web folder on the target Report Server.
Building a report project will deploy reports to a designated target Report Server. The Report Manager
web interface may be used to deploy individual reports manually by simply browsing for and selecting
the RDL file. The Reporting Services Web service may be used to deploy reports programmatically using
methods of this multipurpose object. Chapter 10 will explore each of these options and detail deploy-
ment techniques and related considerations.
Designing and Architecting Report Solutions
Reporting Services does offer an out-of-the-box solution. Reports can be designed in Visual Studio 2005,
deployed to a server, and viewed using the Report Manager web interface quite easily. However, for cus-
tom applications or to meet specific business needs, this may not be the ideal solution. Reporting Services
is an extensible service with several options for designing, managing, deploying, rendering, and deliver-
ing reports to users.
Chapter 12 discusses these options and consider how understanding your business requirements should
lead to the most ideal solution. You will look at different business cases and how a reporting solution fits
into the overall picture to meet business and users' needs now and in the future.
Third-Party Product Integration
Probably one of the most compelling aspects of the Reporting Services extensible architecture is its abil-
ity to integrate seamlessly with business solutions. This means that it can not only become part of a cus-
tom-built business solution but also folds very neatly into commercial product offerings. The SQL Server
database product has become a core component of third-party CRM, financial, ERP, and business analyt-
ics solutions. Now Reporting Services is working its way into many shrink-wrapped products as well.
Reporting Services can be incorporated into a custom application without the user ever knowing that
they are using a different product. It integrates with many development environments so much more
Search WWH ::
Custom Search