Microsoft Office Tutorials and References
In Depth Information
Data processing extensions are used to interact with different data sources. They perform
query operations as they process query requests from the report processor component.
While default data processing extensions are used to connect to many data source types,
you can also write your own custom data processing extension.
Rendering extensions are those that render data and the layout of the report from the
report processor in one of the seven supported formats mentioned earlier. Report Server
processes tables, charts, matrices, and more by default. When you need to add a custom
feature to a report, you can design and create a custom report processing extension.
Delivery extensions are used to deliver reports to specific destinations. For instance,
an e-mail delivery extension delivers a scheduled report to specified e-mail address
through SMTP.
All of these extensions allow users to create custom features in the product. For example, you can create and
install a custom rendering extension to support a new output format. Given all these extensions, on a high level the
Reporting Services service and component architecture looks like what’s shown in Figure 3-1 .
Web Browser
Authoring Tools
Third-party Tools
Service Architecture
Report Server Components
Report Manager
Web Service Components
Report Processor and
Background Processing Applications
Application Management
Windows Services
Memory Management
1: Report Server Database; 2: Data Sources
Figure 3-1. Reporting Services service and component architecture
Information about reports, report properties, and objects are stored in a SQL Server database, which also holds
report models, published reports, and the folder hierarchy managed by Report Server. This database provides internal
storage information for single or multiple report servers. This all arrives as an installation package with SQL Server 2012.
Search JabSto ::

Custom Search