Push vs. pull: Configuring SQL Server replication
Posted by: Denny Cherry
I've published a new artcile over on SearchSQLServer.com. This article is titled "Push vs. pull: Configuring SQL Server...
I've published a new artcile over on SearchSQLServer.com. This article is titled "Push vs. pull: Configuring SQL Server...
The official answer is to delete the subscriber and recreate it pushing a new snapshot to the subscriber. The much quicker and easier method is as follows. 1. Stop the distribution agent on the machine that it's currently running on. 2. Disable the SQL Agent job that runs the distribution...
This is a "it depends" sort of question. These are my recommendations, your mileage may vary. Your distributor is on the same system as your publisher - Pull is probably for you Your Subscribers are a very high transaction count - Push is probably for you You need to manually copy the...
When dealing with a high load replication environment network latency and network traffic can become as issue. There are a few settings you can play with, within the subscription agents themselves such as the –PacketSize, -UseInprocLoader, and –SubscriptionStreams. While working with these...
The error reporting in SQL Server Replication isn't all that great. This is a well known issue that pretty much everyone knows about. Something that I don't know if a whole lot of people know about, is that there is a way to get a lot more information from replication about what's going on, and...
Microsoft's Log Shipping is pretty good. But it requires that you have SQL Server Enterprise Edition on both the machines. This makes the solution fairly expensive. Because of this I've written a replacement which can be used on any edition of SQL Server including SQL Server Express Edition...
