April 16, 2012 at 2:40 pm
I've mentioned here before that we've got a messed up SSRS 2005 environment in production. After struggling with it for a long time, we've decided to just abandon it. We've now got SSRS installed on another server, and users love being able to get reports they've not seen in years.
We'd really love to move the reports off of the old server onto the new one, but try as we might we can't find where the .RDL files are. So, this leads me to ask, when you deploy a .RDL file to the ReportServer web service, where does it go?
(We're working with SSRS 2005.)
Kindest Regards, Rod Connect with me on LinkedIn.
April 16, 2012 at 11:22 pm
When you deploy a report to reporting services, it is actually stored in the ReportServer database. If you need to get a copy of a report, the normal way to do this is download a copy of the report from the reporting services site. You can do this from Report Manage or perhaps by using one of the scripting tools (e.g RS Scripter).
April 17, 2012 at 8:33 am
happycat59 (4/16/2012)
When you deploy a report to reporting services, it is actually stored in the ReportServer database. If you need to get a copy of a report, the normal way to do this is download a copy of the report from the reporting services site. You can do this from Report Manage or perhaps by using one of the scripting tools (e.g RS Scripter).
The Report Manager on the site is seriously hosed; totally worthless. I've not heard of the RS Scripter, but will try and look into it. Thanks.
Kindest Regards, Rod Connect with me on LinkedIn.
April 17, 2012 at 10:52 pm
If all else fails, the RDL is stored in table Catalog in the ReportServer database.
The following SELECT is a start to getting at the RDL
SELECT
Name
,convert (varchar(max), convert (varbinary(max),[Content])) AS ReportRDL
FROM [ReportServer].[dbo].[Catalog]
where TYPE =2
You may need to deal with very long strings (depending on how large the RDL is for each report). Have a look at the other columns in this table - you should be able to reconstruct everything you need if all other options fail you.
And Microsoft does not support direct access of the tables in the ReportServer database. Be careful and make sure that you don't make a bad situation worse by updating the ReportServer database.
April 20, 2012 at 6:49 am
I mean exactly that - don't update the report server database. If report manager is already hosed, you have limited ability to do anything that is supported. Start making changes to the database and you will run a serious risk of make a bad situation worse.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply