Wondering if a dataset can be cached on a schedule to maintain historical data from an application. I know this could be done by exporting the data out and storing it in another database, but I'd really like to just use the SSRS datasets instead of having to create and maintain another database. I'm pretty sure the dataset can be cached, but I don't know if a single report can access multiple cached datasets. Thanks!CraigMartin Edgile, Inc. http://identitytrench.com

Similar question here: http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/25678277-079b-4644-827b-1936b68d3f5d The answer is that chunk data is stored in the SSRS database (which refers to the actual data stored for the report) but this would need to be parsed by VB.NET / ASP.NET to read it out into any meaningful form. Once that was done however, you could use the data pretty much any way you wanted (read into temp / holding tables in a database for example) Rgds Geoff

Thanks for the quick answer. It appears the answer is essentially no, unless you're willing to roll up the sleeves and dig around the SSRS temp DB. For reports requiring the historical data I guess it makes sense to copy the data from the datasource into another database.CraigMartin Edgile, Inc. http://identitytrench.com

No probs - that's right - there's no default way of doing what you're asking without getting under the hood and creating some pretty complex routines (and you'd still need to stick the parsed data somehwere for the report to read anyway) It's obviously a bit old fashioned but there is always the ability to export out to csv files via timed subscriptions and read them into reports as and when necessary...Rgds Geoff