UPDATE – An updated version of this project has been published to codeplex at: http://ssrscatalogqueries.codeplex.com/. The updated version extracts ALL types of content (not just XML, but resources as well) and also exports the folder structure. It’s really cool!
A couple of months back I posted an article on “Extracting SSRS Report RDL (XML) from the ReportServer Database”. Recently, Jason Brimhall posted an article that used similar logic to do a “SSRS Export En Masse”. It’s a great example of how queries against the ReportServer.dbo.Catalog table can be used to recover reports that have been published to the report server, even if you have lost the source files.
Jason’s blog post used a combination of Transact-SQL, a For Each loop, and VB.NET Script task to do the work. As I read through his post, I wondered if the SSIS “Export Column” data flow transform help solve the problem and eliminate VB.NET code. Turns out it can, and it makes for a pretty simple package.
Note, here is the source query I will use for my SSRS content. This is based on the queries discussed in my “Extracting SSRS Report RDL …” blog post. I’ll refer to this query as the “Extract Query” in my list of instructions below.
– BEGIN EXTRACT QUERY —
WITH ItemContentBinaries AS
WHEN 2 THEN ‘Report’
WHEN 5 THEN ‘Data Source’
WHEN 7 THEN ‘Report Part’
WHEN 8 THEN ‘Shared Dataset’
END AS TypeDescription
,CONVERT(VARBINARY(MAX),Content) AS Content
WHERE Type IN (2,5,7,8)
–The second CTE determines the appropriate file extension to use
–plus it strips off the BOM if it exists…
WHEN 2 THEN ‘.rdl’ –Report Definition Language
WHEN 5 THEN ‘.rds’ –Report Data Source
WHEN 7 THEN ‘.rsc’ –Report Server Component (? – Guessing)
WHEN 8 THEN ‘.rsd’ –Report Server Data (? – Guessing)
END AS ExportFileExtension
WHEN LEFT(Content,3) = 0xEFBBBF
END AS Content
–The outer query gets the content in its varbinary, varchar and xml representations…
Name + ExportFileExtension AS ExportFileName
,CONVERT(xml,Content) AS ContentXML
– END EXTRACT QUERY –
Here are the steps I followed. You can download my SSIS project here.
- Create a new Package in an SSIS BIDS Project. I named my new package “Export SSRS Content.dtsx”
- Create a target folder that the SSRS Content will be exported to. I created a folder named “C:\SSRS Content Extracts”
- Add a Variable to the SSIS Package to store the path to the directory you just created as a string. I created a variable named “OutputDirectory” and set its default value to “C:\SSRS Content Extracts\” (note the that I included the trailing slash)
- Add a “Data Flow” task to your control flow. I named mine “SSRS Content Extract”
- Add a Connection Manager that points to the ReportServer database. I named mine “ReportServer DB”
- Add an “OLE DB Source” to your data flow
- I named mine “SSRS Content Source”
- Set it to use the “ReportServer DB” connection manager we just created
- Set the “Data Access Mode” to “SQL Command”
- I pasted the “Extract Query” shown above as the “SQL command text”
- Add a “Derived Column” transform to the dataflow and name it “Generate Export Path”. Drag the green data path from the “SSRS Content Source” to it.
- Double click on the “Generate Export Path” transform and add a derived column with the following properties (don’t include the double quotes around the values shown below):
- Derived Column Name: “ExportPath”
- Derived Column: “<add as a new column>”
- Expression: “(DT_WSTR,2048)(@[User::OutputDirectory] + [ExportFileName])”
- The Data Type and Length will be set for you based on the expression above. (DT_WSTR, 2048)
- Add an “Export Column” transform to the dataflow and name it “Export Content”. Drag the green data path from the “Generate Export Path” transform to it.
- Double click on the “Export Content” transform and configure the values as follows (again, don’t include the double quotes):
- Extract Column: “ContentXML”
- File Path Column: “ExportPath”
- Allow Append: Cleared
- Force Truncate: Checked
- Write Byte-Order Mark: Cleared
There you have it. Pretty simple. A couple of things to note.
- The expression I used in step 8.3 assumes that the “OutputDirectory” variable value includes the trailing forward slash.
- The “Force Truncate” checkbox set in step 10.4 causes existing files to be overwritten
The resulting data flow looks like this:
You can now run this package (and even supply an alternative export path via the OutputDirectory variable) to export all reports, data sources, report parts, and shared datas sets from an SSRS 2008 R2 installation.