Would the solution suggested here: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/774d94ef-c31a-4d90-9289-add0e0961251 be advisable on a scale of hundreds of thousands? We need to keep snapshots of reports but we cannot rely on default parameters (hence the above solution). The reason we are going for snapshots is to provide flexibility in the rendering format.

Hi dob_xml, Thanks for your post. According to your description, you would like to know whether the linked report solution is advisable on a scale of hundreds of thousands. If you requirement is coordinate with the linked thread you post above, linked report is a nice choice for you. Because a report snapshot is relying on default parameters, there is no interactive user to specify these parameter values, you can’t specify it with dynamic values. Moreover, Report snapshots are not saved in a particular render format. Instead, report snapshots are rendered in a final viewing format (such as HTML) only when a user or an application requests it. Deferred rendering makes a snapshot portable: the report can be rendered in the correct format for the calling device or browser. More information about this topic, please refer to the articles below: Linked Reports: http://msdn.microsoft.com/en-us/library/ms156327(SQL.90).aspx Report Snapshots: http://msdn.microsoft.com/en-us/library/aa256337(v=SQL.80).aspx Thanks, Bill Lu Please remember to mark the replies as answers if they help and unmark them if they provide no help.