Bulk Upload Rdl Files to Report Server

April 11, 2022 Post a Comment

I discussed how I needed to update each SQL Server Reporting Services (SSRS) RDL in yesterday's blog post chosen, " What Does the Fault Bulletin, "Unknown Report Version 9.0," in Visual Studio 2015 Mean? " In lodge to update the RDLs I would accept to perform a, "Save Equally," or edit each study. In the closing section of that postal service, I complained that with over 600 reports, I needed to notice a style to bulk upgrade SSRS RDLs from SQL Server 2005 to SQL Server 2008 R2. It took a piffling time and research, but in the stop I stumbled upon a way that may not exist completely automatic, but it'due south even so a keen time saver!
This blog post volition show you lot how to bulk upgrade SSRS RDLs.

The Trouble

Let me begin by reminding you lot about the trouble that I had with the, "Unknown Study Version ix.0," error message. I was upgrading all of my SSRS 2005 solutions and projects to the current SQL Server Data Tools (SSDT) version. Information technology turns out that the current SSDT solution/project can exist upgraded, but the RDLs inside the solution can't be upgraded or saved. The fault generated was, "Unknown Study Version ix.0." As I explained in my previous web log mail service, support ended for SQL Server 2005 in April 2016, so it made sense that the electric current version of SSDT also wouldn't support SQL Server 2005.
Based on this fault bulletin, I determined that a iii-footstep upgrade procedure needed to be performed:
-First, upgrade the SQL Server 2005 solutions/projects to another version of SQL Server, such as SQL Server 2008 R2.
-Next, y'all demand to practise i of the following:
i). Save each report with a new name, which volition also update the SSRS file version, by using, "Save As." In my particular case, I also needed to rename each study back to the original proper noun!
OR
ii). Edit the report and save it as you lot normally would.
-Finally, upgrade the solution and projection to the latest version of SSDT.
To put information technology mildly, this process is a huge hurting.

Majority Upgrade SSRS RDLs

I spent some fourth dimension researching how to perform a bulk upgrade of SSRS RDLs. I even posted a note in the SQL Server SSRS forum. While waiting for someone to answer my question, I decided to try several things on my own. I found one solution that, although not automated, will work without as well much try.
Bulk Upgrade SSRS RDLs - Report Tab
It's really unproblematic! Open your report from the Solution Explorer window in SQL Server Business Intelligence Development Studio (BIDS) SQL Server 2008 R2.
Without making whatsoever changes to the written report, the report tab volition show that the report already has changes to it. You lot can come across this past the asterisk sign, "*," at the end of the tab. One time you salve the study, the report is upgraded automatically to the SQL Server 2008 R2 schema.
Why am I upgrading to SQL Server 2008 R2 instead of the latest version? First, in my experience with upgrading RDLs, at that place are generally fewer problems when upgrading to the side by side version (i.east. 2005 to 2008 R2) instead of upgrading several versions ahead. Second, I already had BIDS 2008 R2 installed in my lab and on my laptop, so let's say it was more than convenient!
Bulk Upgrade SSRS RDLs - Open
Next, in social club to salvage time, select all of the reports inside a project. Right-click and and then select Open. This volition open all of the highlighted reports.
Bulk Upgrade SSRS RDLs - Save All
At present that all of the reports are open and y'all see the asterisk signs (purple arrows), click on the Save All icon to save the reports. This will upgrade all of the RDLs to SQL Server 2008 R2.
Bulk Upgrade SSRS RDLs - Saved Report
One time the reports are saved, the asterisk signs, "*," disappear from report tab!
At present that all of the solutions and projects are upgraded to SQL Server 2008 R2, you can so motility onto the 3rd and concluding step which is upgrading to the current version of SSDT. This will upgrade all of the solutions/projects and all of the RDLs to SQL Server 2016 or SQL Server 2017. Since there are no tricks or catches with that procedure, I'm not covering it here. Once the final upgrade is complete, y'all can edit your solutions, projects and RDLs using the current SSDT.
If you accept any questions, delight feel complimentary to contact me @GarthMJ .
Do y'all have an thought for a blog postal service nearly a Configuration Manager (SCCM) query or reporting topic? Let me know. Your thought might become the focus of my next web log postal service!