MS SQL Reporting Services (报表服务) 2008 Tip

安装完RS 2008，在IIS中并没有ReportServer / Reports 应用目录 - RS 2008已经不再依赖于IIS:

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="ProgId" content="Word.Document"> <meta name="Generator" content="Microsoft Word 12"> <meta name="Originator" content="Microsoft Word 12"> <link rel="File-List" href="file:///C:%5CUsers%5CJAMESZ%7E1.SSW%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"> <link rel="themeData" href="file:///C:%5CUsers%5CJAMESZ%7E1.SSW%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"> <link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CJAMESZ%7E1.SSW%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"> <style>  </style>

Reporting Services no longer depends on IIS to provide access to the SOAP endpoint. URLs no longer include Web sites in IIS. Reporting Services uses HTTP.SYS directly to listen for requests on a specific port that you define for report server URLs.

http://msdn.microsoft.com/en-us/library/ms143380.aspx

老板Adam在TechEd Australia做演示时，发现了一个有趣的问题：在 RS 2005 和 RS 2008下运行同样的报表，通过任务管理器发现，两个进程使用内存数量存在显著不同：

RS 2005 - 17 MB
RS 2008 - 127 MB!

微软Robert Bruckner的回答：

<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="ProgId" content="Word.Document"> <meta name="Generator" content="Microsoft Word 12"> <meta name="Originator" content="Microsoft Word 12"> <link rel="File-List" href="file:///C:%5CUsers%5CJAMESZ%7E1.SSW%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"> <link rel="themeData" href="file:///C:%5CUsers%5CJAMESZ%7E1.SSW%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"> <link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CJAMESZ%7E1.SSW%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"> <style>  </style>

Note that in RS 2005, live reports are executed by the RS web service which runs inside IIS/W3WP. ReportingServicesService.exe in RS 2005 essentially only executes scheduled subscriptions, but not live reports. Consequently in your scenario, the memory consumption of ReportingServicesService.exe in RS 2005 stays low.

In RS 2008, ReportingServicesService.exe hosts everything in one process (i.e. RS web service functionality, report manager, and scheduled subscriptions). That’s why memory consumption goes up for executing reports.

Btw, since this is mainly managed code, memory consumption reported in task manager will not immediately go down after a report is rendered. It is up to the garbage collector to reclaim the released memory. You might want to look at committed bytes CLR performance counter of the ReportingServicesService.exe process to get more accurate numbers than task manager.