Planning the Database Server Infrastructure

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Because RMS uses databases and stored procedures to support its operations, a database infrastructure is required to use RMS in your organization. Your database server may be on the same server as RMS or a different server. If you do not have a database server in your infrastructure to support RMS, you can use the Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Release A or Microsoft SQL Server 2005 Express Edition as the database server to test RMS.

It is recommended that these products be used to support RMS databases only in test environments because they do not include the tools necessary to fully operate and support an enterprise wide database. Additionally, because MSDE or SQL Server 2005 Express Edition does not support remote networking, you must install it on the same server as RMS and you cannot add additional RMS servers to the RMS cluster. The terms of use for these products specify that you cannot use SQL Server client tools to manipulate a Microsoft SQL Server Desktop Engine or SQL Server 2005 Express Edition database. With this restriction you will be unable to backup and restore the RMS configuration database, view logging information or directly modify data stored in the configuration database.

If you plan to have your databases on a different server than your RMS installation, you need to use a full database server product, such as SQL Server to provide the database support. Be sure that you provide the RMS service account with the appropriate permissions to read, write, and create databases that are on the database server that you use to support RMS.

RMS is designed for and tested with database servers running Microsoft SQL Server 2000 and Microsoft SQL Server 2005. RMS can run on other database servers if they comply with the following criteria:

  • Must support ADO.NET interfaces provided by the Microsoft .NET Framework.

  • The database server must be Transact-SQL compliant because RMS initialization scripts and RMS stored procedures use Transact-SQL.

  • The database server must support all Microsoft SQL Server specific extensions.

  • The database provider must be able to respond to method calls of the System.Data.SqlClient namespace of the .NET Framework.

  • The database provider must be able to provide the corresponding functionality of the System.Data.SqlClient namespace.

  • Use Windows Authentication Mode.

The database provider must be able to find out if the database server supports the above criteria, contact the relevant database vendor.


All RMS databases are created with Full recovery on by default, but there are no transaction log backup jobs created to truncate the log files after a certain period of time. This can cause the hard disk of your server to become full and lead to a database server failure. Full-recovery is recommended for the DRMS_configuration database, the other DRMS databases can be configured to use a different recovery model as appropriate for your organization.

This section covers: