We have Transactional Replication running from SQL Server 2005 to 2012 (both standard editions). The distributor sits with the subscriber on the SQL2012 machine. Since we fired it up we have been gettingsporadic failures of data import SPs. By sporadic I mean cca. 1 failure in 20-30 executions. The error message is:
Schema change failed on object '[dbo].[TableA]'. Possibly due to active snapshot or other schema change activity.
But...
Due to active snapshot? - We don't use the Snapshot Agent; it is disabled.
Other schema change activity? - We are getting these failures since we started using replication and we are doing just as much schema changes at the moment as we had been doing before replication was started.
The schema changes the SPs do are along these lines:ALTER TABLE dbo.TableA NOCHECK CONSTRAINT Constr1 --insert some stuff etc. ALTER TABLE dbo.TableA CHECK CONSTRAINT Constr1
or
ALTER TABLE dbo.TableA DISABLE TRIGGER ALL
Triggers, check constraints are NOT replicatied.
The question is then: Why are we getting this?
The parameters of the publication for your reference:
pubid 1
restricted 0
status 1
task 1
replication frequency 0
synchronization method 3
immediate_sync 0
enabled_for_internet 0
allow_push 1
allow_pull 0
allow_anonymous 0
independent_agent 1
immediate_sync_ready 0
allow_sync_tran 0
autogen_sync_procs 0
snapshot_jobid 0xFFFF
retention 0
has 1
subscription
allow_queued_tran 0
snapshot_in_defaultfolder 1
alt_snapshot_folder NULL
pre_snapshot_script NULL
post_snapshot_script NULL
compress_snapshot 0
ftp_address NULL
ftp_port 21
ftp_subdirectory NULL
ftp_login anonymous
allow_dts 0
allow_subscription_copy 0
centralized_conflicts NULL
conflict_retention 14
conflict_policy NULL
queue_type NULL
backward_comp_level 40
publish_to_AD 0
allow_initialize_from_backup 0
replicate_ddl 1
enabled_for_p2p 0
publish_local_changes_only 0
enabled_for_het_sub 0