Product Documentation

Secondary database locations

May 28, 2016

By default, the Configuration Logging and Monitoring databases (the secondary databases) are located on the same server as the Site Configuration database. Initially, all three databases have the same name. Citrix recommends that you change the location of the secondary databases after you create a Site. You can host the Configuration Logging and Monitoring databases on the same server or on different servers. The backup strategy for each database may differ.

When you change the location of the Configuration Logging or Monitoring database:
  • The data in the previous database is not imported to the new database.
  • Logs cannot be aggregated from both databases when retrieving logs.
  • The first log entry in the new database indicates that a database change occurred, but it does not identify the previous database.

Before you change the location of the Configuration Logging or Monitoring database, install a supported version of Microsoft SQL Server on the server where the database will reside. Set up mirror, cluster, or other supported redundancy infrastructures, as needed.

You cannot change the location of the Configuration Logging database when mandatory logging is enabled.

Note: You cannot use this method to change the location of the Site Configuration database.
  1. Select Configuration in the Studio navigation pane. The names and addresses of the three databases are listed, plus mirror server addresses, if configured.
  2. Select the database for which you want to specify a new location and then select Change Database in the Actions pane.
  3. Specify the location of the server containing the new SQL Server installation (using one of the forms in the following table) and the database name.
    Database type What to enter With this database configuration
    Standalone or mirror servername The default instance is used and SQL Server uses the default port.
      Servername\INSTANCENAME A named instance is used and SQL Server uses the default port.
      servername,port-number The default instance is used and SQL Server uses a custom port. (The comma is required.)
    Other cluster-name A clustered database.
      availability-group-listener An Always-On database.
  4. If you want Studio to create the database, click OK. When prompted, click OK, and Studio will create the database automatically. Studio attempts to access the database using the current Studio user's credentials; if that fails, you are prompted for the database user's credentials. Studio then uploads the database schema to the database. (The credentials are retained only for the database creation time frame.)
  5. If you want to create the database manually, click Generate script. The generated scripts includes instructions for manually creating the database and a mirror database, if needed. Ensure that the database is empty and that at least one user has permission to access and change the database before uploading the schema.