New answers tagged

0

If you have 1 billion changes, have you looked into replicate the execution of a stored proc? Replicate execution of stored procedure will save yourself a lot of time and space and reduce the exact scenario you are hitting, where distribution db is filled with commands. If this is some kind of batch process, then marking the stored proc as replicated, it ...


2

With 1 billion changes, I would be worried about the size of TempDB when the row version is added to everything. Hilary Cotter responded to this same question here - https://social.msdn.microsoft.com/Forums/sqlserver/en-US/2edbdc37-c2ed-4c84-ae72-16f89404172b/sql-server-replication-and-enabling-readcommittedsnapshot-on-the-distributor?forum=sqlreplication. ...


1

Do I treat the subscribers just like a normal database and perform maintenance via a maintenance plan on them - or should they be left alone / treated any differently? Yes, subscriber databases should be treated as regular user databases & you should intelligently perform Index maintenance (and do backups as well) . Infact, replication does not ...


0

I don't know how your drop the article from publication, but you can assign again just execute this exec sp_addsubscription @publication='your_pub',@article='all',@subscriber='your_server'


0

An alternative would to remove the article from the publication and re add, causing a new snapshot to be taken of the table. This way there's no question whether the right data is in the subscriber. To do this you need to make sure the publication properties are set to FALSE for allow_anonymous and immediate_sync - if either of these are true then the a ...


3

MSDTC provides transaction management services for applications. It can act as a regular transaction manager or an XA-compliant resource manager. SQL Server is the well known app that uses DTC but it isn't really a SQL Server feature or even component. MSDTC is really intended to provide transaction management for two or more distinct resources to ensure ...


6

I had to finally call Microsoft support and just a simple command called DBCC LOG INFO on publisher revealed a possible root cause. I saw more than 8600 VLFs! and this was the cause of that latency. Also, our log file is preallocated to 538GB. Replication was out of sync by almost 19 hours by the time I got follow up call from Microsoft help 4:00pm ...



Top 50 recent answers are included