Converse agora com nosso suporte
Chat com o suporte

Change Auditor - For Advanced Users 7.2 - Technical Insight Guide

Change Auditor Services Change Auditor licensing processes Component Start-up Considerations Change Auditor network communications Coordinator internal tasks Registry Settings Change Auditor built-in fault tolerance Change Auditor protection Database Considerations Account exclusions best practices

How to move the Change Auditor database and coordinator to another server

Select Tasks | Detach.
On the General page of the Attach Databases screen, click Add and select the database you copied over.

If you plan to replace the old Change Auditor coordinator/server, install a newer version of Change Auditor and it connects your existing agents to the new Change Auditor server without a problem. Make sure that you join the existing installation.

Use the following steps if your SQL database is already on another server and you do not plan to move it. This scenario installs a second Change Auditor coordinator and then disables and uninstalls the first one. All agents transition over to the new Change Auditor server.

How to estimate the required SQL server disk space

The Change Auditor database (version 6.x or later) can grow indefinitely without a decrease in performance. This makes it unnecessary to create periodic archives.

Adequate disk space should be reserved to accommodate the volume of events dictated by your compliance and retention policies. Testing shows that events take approximately 8,000 bytes per event.

In addition to the volume of events, the type of events and the volume of alerting also affect disk consumption. To predict disk consumption for your intended retention period, configure Change Auditor as you intend to use it in your environment for a period sufficient to project long-term space requirements.

How SQL Server Autogrow affects Change Auditor

The Change Auditor database (version 6.x or later) is created with SQL Server Autogrowth set to 10%. This may cause issues for large databases that require an extended amount of time to grow the database.

If you begin to see frequent timeouts in the coordinator log, check the SQL Errorlog for “Autogrow of file ‘ChangeAuditor’ in database ‘ChangeAuditor’ was cancelled by user or timed out after 30121 milliseconds.” to confirm that it is related to Autogrowth. If you see this error, consider changing the Autogrowth setting to a smaller value or implementing “Instant File Initialization” on the SQL server hosting the Change Auditor database. You can also pre-allocate a larger size for the Change Auditor database manually.

How to query an archive database

To query an archive database (version 6.x or later), you need to:

On the Manage Connection Profiles dialog, select Add to start the Connection wizard.

An easy way to configure the appropriate SQL security for all users is to add them to the appropriate Change Auditor database role that is created during the coordinator installation. Essentially you will use the Change Auditor security groups that were created during the coordinator installation. Create corresponding SQL logins for these two groups, and then assign each of those logins the appropriate database role for each of the archive databases:

For more information about adding accounts to the Change Auditor database role, see the Change Auditor Installation Guide.



Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação