The rs.exe utility processes script you provide in an input file. Use this utility to automate report server deployment and administration tasks.
Beginning with SQL Server 2008 R2, the rs utility is supported against report servers that are configured for SharePoint integrated mode as well as servers configured in native mode. Previous versions only supported native mode configurations.
(Required) Specifies the .rss file to execute. This value can be a relative or fully qualified path to the .rss file.
(Required) Specifies the Web server name and report server virtual directory name to execute the file against. An example of a report server URL is http://examplewebserver/reportserver. The prefix http:// or https:// at the beginning of the server name is optional. If you omit the prefix, the report server script host tries to use https first, and then uses http if https does not work.
(Optional) Specifies a user account used to connect to the report server. If -u and -p are omitted, the current Windows user account is used.
(Required if -u is specified) Specifies the password to use with the -u argument. This value is case-sensitive.
(Optional) Specifies the SOAP endpoint against which the script should run. Valid values are the following:
(Optional) Specifies the number of seconds that elapse before the connection to the server times out. The default is 60 seconds. If you do not specify a time-out value, the default is used. A value of 0 specifies that the connection never times out.
(Optional) Specifies that the commands in the script file run in a batch. If any commands fail, the batch is rolled back. Some commands cannot be batched, and those run as usual. Only exceptions that are thrown and are not handled within the script result in a rollback. If the script handles an exception and returns normally from Main, the batch is committed. If you omit this parameter, the commands run without creating a batch. For more information, see Batching Methods.
(Optional) Specifies global variables that are used in the script. If the script uses global variables, you must specify this argument. The value that you specify must be valid for global variable defined in the .rss file. You must specify one global variable for each –v argument.
The -v argument is specified on the command line and is used to set the value for a global variable that is defined in your script at run time. For example, if your script contains a variable named parentFolder, you can specify a name for that folder on the command line:
Global variables are created with the names given and set to the values supplied. For example, -v a="1" -v b="2" results in a variable named a with a value of"1" and a variable b with a value of "2".
Global variables are available to any function in the script. A backslash and quotation mark (\") is interpreted as a double quotation mark. The quotation marks are required only if the string contains a space. Variable names must be valid for Microsoft Visual Basic; they must start with alphabetical character or underscore and contain alphabetical characters, digits, or underscores. Reserved words cannot be used as variable names. For more information about using global variables, see Built-in Collections in Expressions (Report Builder and SSRS).
To run the tool, you must have permission to connect to the report server instance you are running the script against. You can run scripts to make changes to the local computer or a remote computer. To make changes to a report server installed on a remote computer, specify the remote computer in the -s argument.
You can define scripts to set system properties, publish reports, and so forth. The scripts that you create can include any methods of the Reporting Services API. For more information about the methods and properties available to you, see Report Server Web Service.
The script must be written in Visual Basic .NET code, and stored in a Unicode or UTF-8 text file with an .rss file name extension. You cannot debug scripts with the rs utility. To debug a script, run the code within Microsoft Visual Studio.