Configuration Logging is enabled, and mandatory logging is disabled.
Configuration Logging uses the database that is created when you create a Site
(also known as the
Configuration Database). Citrix recommends that you change the location
of the database used for Configuration Logging (and the database used for the
Monitoring Service, which also uses the Site Configuration Database by default)
after creating a Site, for the following reasons:
- The backup
strategy for the Configuration Logging Database is likely to differ from the
backup strategy for the Site Configuration Database.
- The volume of
data collected for Configuration Logging (and the Monitoring Service) could
adversely affect the space available to the Site Configuration database.
- It splits the
single point of failure for the three databases.
For more information, see
Change secondary database locations.
Configuration Logging Database supports the same high availability features as
the Site Configuration Database. Review the database guidance in
Plan a deployment.
the Configuration Logging Database location
- Create a
database server, using a supported SQL Server version.
- From Studio,
Logging in the left pane.
- In the
Actions pane, click
Configuration Logging dialog box appears.
logging database. The
Configuration Logging Database dialog box appears.
- Specify the
location of the server containing the new database server (using one of the
forms in the following table) and the database name.
||What to enter
||With this database configuration
|Standalone or mirror
||The default instance is used and SQL Server uses the default
||A named instance is used and SQL Server uses the default port.
||The default instance is used and SQL Server uses a custom port.
(The comma is required.)
||A clustered database.
||An Always-On database.
- If you want
Studio to create the database, click
connection. 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.)
- If you want to
create the database manually, click
Generate script (or use Get-LogDBSchema in the
PowerShell SDK). The generated script includes instructions for manually
creating the database. Ensure that the database is empty and that at least one
user has permission to access and change the database before uploading the
Configuration Logging 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 Configuration Logging Database will indicate
that a database change occurred, but it does not identify the previous