Return
-
Title
Should Coordinators located close to SQL server or remote sites based on Agent locations -
Description
The purpose of this KB is to have best practice for where to locate Coordinators when multiple are deployed in the environment. -
Resolution
In general, it is best to locate the Coordinators as close as possible to the SQL instance where Change Auditor database resides. This will help ensure reliable bandwidth and low latency when dealing with Coordinator/SQL transactions.This is of course is rule which has exceptions such as multi-forest deployments, DMZ requirements, etc. where based on product architecture Coordinators may need to be deployed remotely to SQL.If running Coordinator in remote scenario with high latency to SQL consider the following Coordinator SQL timeout registry keys if frequent timeout warnings are encountered in the Coordinator service log file:SQL Timeout (general timeouts)https://support.quest.com/technical-documents/change-auditor-for-advanced-users/6.7/technical-insight-guide/coordinator-registry-settings/sql-command-timeoutBulk SQL Timeout (event insertion)https://support.quest.com/change-auditor/kb/119156The suggested value to start for both registry key values is 300 (5 minutes).