Quantcast
Channel: SQL Server Replication forum
Viewing all articles
Browse latest Browse all 4054

Preventing transaction replication to be broken after a big update/delete query runs

$
0
0

Hi experts,

For one of our env, for the transaction replication set up:

Publisher: (prod OLTP DB server) SQL server 2005, Database[DB]size : 220 GB also act as the distributor 

Subscriber (Prod reporting DB server) : SQL server 2005  , DB gets replicated and is currently in sync.

Now, as per the yearly activity there would  be a script run on OLTP publisher to delete more than 1816009 records..

Now will this break replication? Or is there a way i can prevent one because setting that up is tedious?

Also, something similar was done 2 years back and we only have the error as

"

"The process could not execute 'sp_replcmds' on 'xxxxxx'." "Status: 2, code: 0, text: 'Timeout expired'" "A time out occurred while waiting for memory resources to execute the query." "Agent 'xxx' is retrying after an error. 0 retries attempted. See agent job history in the Jobs folder for more details." "The step was cancelled (stopped) as the result of a stop job request""

But we do not have any solution listed and will this break if we do it this time, just curious how can i move from here?

Thanks..




Viewing all articles
Browse latest Browse all 4054

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>