Delen via

  • Artikel

Report Server Command Prompt Utilities

SQL Server Reporting Services includes three command line utilities that you can use to administer a report server. These utilities are installed automatically when you install a report server.

Note

If you prefer to use a tool that has a graphical user interface, you can use the Reporting Services Configuration tool instead of rsconfig and rskeymgmt.

Rsconfig Utility

The rsconfig utility is used to configure and manage a report server connection to the report server database. You can also use it to specify a user account to use for unattended report processing. For more information, see Administration (Reporting Services). To learn more about connection configuration, see Configuring a Report Server Database Connection.

Rskeymgmt Utility

The rskeymgmt utility is an encryption key management tool. You can use it to back up, apply, recreate, and delete symmetric keys. You can also use this tool to attach a report server instance to a shared report server database. Rskeymgmt can be used in database recovery operations. You can reuse an existing database in a new installation by applying a back up copy of the symmetric key. If the keys cannot be recovered, this tool provides a way to delete encrypted content that you no longer use. To learn more about key management and storage of sensitive data, see Storing Encrypted Report Server Data and Configuring and Managing Encryption Keys.

Rs Utility

The rs utility is a script host that you can use to perform scripted operations. Use this tool to run Microsoft Visual Basic scripts that copy data between report server databases, publish reports, create items in a report server database, and more. To learn more about using scripts to administer a server, see Scripting Deployment and Administrative Tasks.

Note

With SQL Server 2008 R2 and later, the rs utility is supported against report servers that are configured for SharePoint integrated mode as well as well as servers configured in native mode. Previous versions only supported native mode configurations.