Can the TraceCacheDatabase option be limited to a single server?
bmay
Posts: 2 Bronze 1
Hi,
I'm using a change log database for SQL Source Control, as described in this article (https://documentation.red-gate.com/soc/configuring/log-changes-to-shared-databases), for one database server. I also have a couple other servers that don't have that ChangeLog database, but they are still trying to put changes into that database, so my logs are full of "'ChangeLog' does not exist" errors.
Is there a way to specify that I want the TraceCacheDatabase setting to only be used for the 1 database server?
This is what my RedGate_SQLSourceControl_Engine_EngineOptions.xml file looks like.
I'm using a change log database for SQL Source Control, as described in this article (https://documentation.red-gate.com/soc/configuring/log-changes-to-shared-databases), for one database server. I also have a couple other servers that don't have that ChangeLog database, but they are still trying to put changes into that database, so my logs are full of "'ChangeLog' does not exist" errors.
Is there a way to specify that I want the TraceCacheDatabase setting to only be used for the 1 database server?
This is what my RedGate_SQLSourceControl_Engine_EngineOptions.xml file looks like.
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <!----> <EngineOptions version="3" type="EngineOptions"> <TraceCacheDatabase>ChangeLog</TraceCacheDatabase> </EngineOptions>And I am currently on SQL Source Control Version 7.6.13.17388
Tagged:
