Skip to main content

SQL Server Report Server Migration - Step by Step Guide

Scenario :

Source SQL Server Reporting Instance : SQL Server 2008/12/14/16

Destination SQL Server Reporting Instance : SQL Server 2008/12/14/16

Solution : 

There are two methods for the  migration of reporting server from One instance to another. The easiest method and the hardest method. You may choose the hardest method if you want to consolidate multiple report servers into single. And if you are willing to have multiple report servers in your environment, go ahead with the easiest method.

1) Easiest method : Database Migration
2) Hardest method : Reports Migration

1) Easiest method : Database Migration
 Setps to follow : 
  • Backup the Source Reporting Server Databases : e.g. ReportServer and ReportServerTempDB
  • Backup the Encryption key from Source Reporting server instance
  •  
  • Restore the Database on destination reporting server SQL Instance (Not required if you want to keep the existing Database server same.
  • Restore the Encryption key on Destination Reporting server instance
  •  
  •  
  • Do the remaining configurations like URL for Report Manager, SMTP, Service Account etc.
  • It done.
2) Hardest method : Reports Migration
Please go thru the below link for reference :
https://msdn.microsoft.com/en-us/library/dn531017.aspx 

Native Mode Report Server to Native Mode Report Server

rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p password -v ts="http://TargetServer/reportserver" -v tu="Domain\Userser" -v tp="password" -v security="True"  

Native Mode to SharePoint Mode – root site

rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p Password -v ts="http://TargetServer/_vti_bin/ReportServer" -v tu="Domain\User" -v tp="Password"  

SharePoint Mode to SharePoint Mode –‘bi’ site collection

rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/_vti_bin/reportserver -v st="sites/bi" -v f="Shared Documents" -u Domain\User1 -p Password -v ts="http://TargetServer/sites/bi/_vti_bin/reportserver" -v tst="sites/bi" -v tf="Shared Documents" -v tu="Domain\User" -v tp="Password" 

Native Mode to Native Mode – Windows Azure Virtual Machine

rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\user1 -p Password -v ts="http://ssrsnativeazure.cloudapp.net/ReportServer" -v tu="user2" -v tp="Password2" 
 
If you want to enable debugging for the Reporting server, open Report Server configuration file from the Report Server installation location
For my case it is : 
D:\Program Files\Microsoft SQL Server\MSRS13.2014_RS\Reporting Services\ReportServer\bin

Open file "ReportingServicesService.exe.config"

Make the changes as shown in below line : 
    <add name="DefaultTraceSwitch" value="4" />
    <add name="Components" value="all:4" />

You may trace the log files in below location : 
D:\Program Files\Microsoft SQL Server\MSRS13.2014_RS\Reporting Services\LogFiles

IMP Note : In this migration, your Developer needs to work hard to input the password in each report as all above mentioned command does not migrate the passwords.
In our case it was running into Thousands.

Hope you got the basic understanding of migration methods of the SQL Server Reporting server

Feel free to reach out to me in case you stuck some where...

Cheers!

- Ashish Kesarkar
India

Comments

Post a Comment

Popular posts from this blog

Solved | SendGrid SSL CERTIFICATE_VERIFY_FAILED certificate verify failed | self signed certificate in certificate chain

Error :   PS C:\Ashish> & "C:/Program Files/Python39/python.exe" c:/Folder/SendEmail.py Traceback (most recent call last):   File "C:\Program Files\Python39\lib\urllib\request.py", line 1346, in do_open     h.request(req.get_method(), req.selector, req.data, headers,   File "C:\Program Files\Python39\lib\http\client.py", line 1279, in request     self._send_request(method, url, body, headers, encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1325, in _send_request     self.endheaders(body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1274, in endheaders     self._send_output(message_body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1034, in _send_output     self.send(msg)   File "C:\Program Files\Python39\lib\http\client.py", line 974, in send     self.connect()   File "C:\Program Files\P

Change EMC Storage Management IP Address without Storage Reboot

Issue :  - How to Change EMC Storage Management IP Address without Reboot - Customer needs to change the IP address, subnet mask , default gateway of a CLARiiON or VNX for Block storage processor (SP)without rebooting the Storage Processors (SP) Scenario : EMC CLARiiON or VNX BLOCK Storage System Solution : 1) Download and Install Naviseccli utility  2)Run following command Add Security Parameters For SPA naviseccli -User admin -Password password -Address 172.XX.XX.XX -Scope 0 -AddUserSecurity For SPB naviseccli -User admin -Password password -Address 172.XX.XX.XX -Scope 0 -AddUserSecurity Get the info about existing SPs For SPA naviseccli -h 172.XX.XX.XX networkadmin -get For SPB naviseccli -h 172.XX.XX.XX networkadmin -get Change the IP Address For SPA naviseccli -h 172.XX.XX.XX networkadmin -set -address 172.XX.XX.XX -subnetmask 255.255.255.0 -gateway 172.XX.XX.XX naviseccli -h 172.XX.XX.XX networkadmin -set -address 172.XX.XX.XX -subnetmask 255.255.255

Fixed | WSUS 2016 | Error Code 0x8024401c | Windows 10 | Windows Server 2016

Scenario : Server : Windows WSUS Server 2016 Client : Windows 10, Windows Server 2016 Error Code :  0x8024401c on Windows 10 or Windows Server 2016 Solution : 1) Go to IIS Manager on WSUS Server 2) Goto Advance Settings of  WsusPool. 3) Make sure following settings are present/configured on the Pool, if not change it to below: Queue Length: 25000 Limit Interval (minutes): 15 "Service Unavailable" Response: TcpLevel Private Memory Limit (KB): 0 4) Make sure, the WSUS Entry in the Registry is having fully qualified domain name of WSUS Server. 5) Stop the IIS 6) Edit the web.config located at following location on WSUS Server : C:\Program Files\Update Services\WebServices\ClientWebService\web.config Replace <httpRuntime maxRequestLength="4096" /> with <httpRuntime maxRequestLength="204800" executionTimeout="7200"/> 7) Start the IIS 8) Retry updating clients. Done! Let me know if it has helped to y