September 27, 2016 at 7:31 am
Hi all,
2014 EE SP1 Availability Group. The AG consists of 1 Windows Server Failover Cluster (WSFC) with 2 VM's on the local site and one VM on a remote.
We have restored and updated a database from a 2005 EE server - the database was in 2000 compat. mode and is now 2014. This was replicated to a 2012 box on the original server, but while I can configure other databases on the WSFC to replicate without issue, when attempting to configure this on the new box it's failing when
use master
exec sp_replicationdboption @dbname = N'MyDBName', @optname = N'publish', @value = N'true'
is run with the following error
Msg 208, Level 16, State 1, Procedure Audit_DDL, Line 20
Invalid object name 'master.dbo.Audit_DDL_Events'.
use master
exec sp_replicationdboption @dbname = N'MyDBName', @optname = N'publish', @value = N'false'
gives
The replication option 'publish' of database 'MyDBName' has been set to false.
FWIW
I've googled myself daft and nothing seems to present itself. I'd be very grateful for and advice or suggestions as to what the problem may be
ta
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
September 27, 2016 at 9:09 am
For the benefit of any future unwary victims.
The Audit_DDL_Events table is one that is used by DDL triggers for tracking changes, and presumably is only set up when you create a DLL trigger - rather than out of the box. SO, when you merely copy over a database with one in, the table's not created in master. Then when you run replication setup, this fires the DDL trigger, which has nowhere to log the event, and went pecs up as a result.
So, in this case, either disable the DDL trigger or recreate it (presumably - not actually checked it as I just disabled it).
There's a chunk of my life I'm not getting back :crazy:
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply