To use the tool simply double click the RSSCripter.exe file. If
presented with an 'Open File - Security Warning' acknowledge the warning
by clicking Run and the tool will open.
Once the tool is open click the Options button to configure the tool for your environment.
Be sure to set the Default Script Directory, this is the location the
tool will put the generated script files in. Next click the Servers tab
to add your reporting servers to the grid. The first column is just a
label and can be anything you like, but it must be unique. The second
column is the actual link to the reporting server and should be of the
form http://servername/Reportserver/ReportService.asmx for SQL 2000
servers and http://servername/Reportserver/ReportService2005.asmx for
SQL 2005 and 2008.
I am not going to go through each tab; the tool includes a very good
readme that describes all the available options. There are a few things
to note. To include report subscriptions click the Report tab and check
the Include Subscriptions check box. The Global tab is used to define
the location of the RS.EXE file, the database authentication and the
scripting mode. Once all options have been set you are ready to run the
tool.
First select a server from your server list by clicking the drop down labeled Report Server. Once a server is selected click the Get Catalog button. This will list all the catalog items on the reporting server.
You can select individual reports by expanding the report folder and
selecting the report or select the entire folder. Once you have selected
the objects click the Script button and the script files will be
generated in the folder selected as the Default Script Directory. The
tool will create script files for all objects selected and it will
create a command (.cmd) file for loading those objects on a server. In
the command file there is a line that sets the URL of the server to
script the report objects to, change this line to the server you want to
transfer your reports to:
Also be sure the line for the location to the RS.EXE file is correct.
Once the command file has been edited copy all the files to the new reporting server and execute the command file by double clicking the file in Windows 2003 and right clicking and selecting Run As Administrator in Windows 2008. When I used this tool to migrate to the new server 136 items were migrated and it took just a few minutes. When I inspected the new reporting server and compared it to the old all items I ask for were on the new server, intact and functioned the same as on the old server.
First select a server from your server list by clicking the drop down labeled Report Server. Once a server is selected click the Get Catalog button. This will list all the catalog items on the reporting server.
SET REPORTSERVER=http://servername/ReportServer
Also be sure the line for the location to the RS.EXE file is correct.
SET RS="C:\Program Files\Microsoft SQL Server\90\Tools\Binn\RS.EXE"
Once the command file has been edited copy all the files to the new reporting server and execute the command file by double clicking the file in Windows 2003 and right clicking and selecting Run As Administrator in Windows 2008. When I used this tool to migrate to the new server 136 items were migrated and it took just a few minutes. When I inspected the new reporting server and compared it to the old all items I ask for were on the new server, intact and functioned the same as on the old server.
Next Steps
- Download the Reporting Services Scripter tool.
- Unzip the file to a folder.
- As always test on a test server before using in production.
- Double click RSScripter.exe, click the Options button and configure the tool.
- After executing, copy the generated files to the new server edit and execute the .cmd.
- Inspect the new server.
- For more information check these references.
No comments:
Post a Comment