Before enabling compression for the Change Auditor database, you must ensure your server which hosts the Change Auditor database has enough CPU resources. Do not apply SQL Compression if your server is very busy and is showing a very high CPU usage.
In the following states, you can benefit from applying SQL Compression to the Change Auditor database:
The largest tables in a Change Auditor database typically are as follows:
TableName |
[dbo].[AuditEvent] |
[dbo].[AuditEvent_EventID] |
[dbo].[AuditEvent_IX_ActionID] |
[dbo].[AuditEvent_IX_AgentID] |
[dbo].[AuditEvent_IX_DomainID] |
[dbo].[AuditEvent_IX_EventClassID] |
[dbo].[AuditEvent_IX_FacilityID] |
[dbo].[AuditEvent_IX_RepositoryID] |
[dbo].[AuditEvent_IX_ResultID] |
[dbo].[AuditEvent_IX_ServerFQDN] |
[dbo].[AuditEvent_IX_SeverityID] |
[dbo].[AuditEvent_IX_SiteID] |
[dbo].[AuditEvent_IX_SubsystemID] |
[dbo].[AuditEvent_IX_TimeBatched] |
[dbo].[AuditEvent_IX_UserName] |
[dbo].[AuditEvent_IX_UserSID] |
As the SQL Compression contains Page Compression and Row Compression, a DB administrator would need to analyze the U (Update) and S (Scan) values of the tables, and then decide which compression method one should use for each table.
Please read this article from Microsoft to get more information related to the U and S values:
https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008/dd894051(v=sql.100)?redirectedfrom=MSDN
Below is a more recent article about SQL Server compression in general:
https://docs.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression?view=sql-server-ver15
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center