SSRS: Report Rendering

Once the intermediate format report has been generated (or retrieved from cache) by the Report Processor, it is delivered to a rendering extension for translation to the end-user requested format. Reporting Services comes standard with seven rendering extensions. Each supports one or more report formats. Custom rendering extensions are also supported, although Microsoft does not encourage their development. Custom rendering extensions typically involve a large development cost.

RENDERING EXTENSION FORMATS SUPPORTED

HTML HTML 4.0 (default) , MHTML

CSV -  Excel-optimized CSV (default) , CSV-compliant CSV
XML -  XML
Image - TIFF (default) ,BMP, EMF , GIF ,JPEG,PNG , WMF
PDF -  PDF 1.3
Excel -  Excel (XLSX)
Word  - Word (DOCX)

 

Parameters affecting how each rendering extension generates the final report are known as

device information settings. Default settings for each rendering extension can be set in the
rsreportserver.config fi le. These can be overridden as part of a specific request to deliver the report in the precise format required.

It is important to note that the Report Processor does not simply hand over the intermediate format report to a rendering extension. Instead, the processor engages the rendering extension, which, in return, accesses the intermediate report through the Rendering Object Model (ROM) exposed by the Report Processor.
The ROM has retained the same basic structure since the release of Reporting Services 2008 and has many benefits. The most significant of these is improved consistency between online and print versions of a report and reduced memory consumption during rendering.


Label: SSRS Interview Questions, SSRS Interview Question and answer.