Nakul Vachhrajani (3/29/2011)

---

Kathy Massey (3/28/2011)

---

We are testing if our Server goes down how long would it take to be back up & running.

Scenario - Transaction Replication Server1 is Publisher/Distributor

Replication runs...

You are right, this feature is no longer supported. You can set up replication and could ALTER the insert/update replication procedures on the subscriber.

This will add and administrative...

This is quite a difficult one to diagnose. From your post I read it as you're using a subscriber as a DR server and have since dropped this out...

I hope you manage to get it sorted but it looks like you're the right track to get it resolved.

One other thought, was there a new software release/update around the...

There are two things I'd probably recommend initially. Reduce the number of Virtual Logfiles you have. 14740, Thats a LOT! and it will reduce log file performance for...

Those look like the default parameters. Do you encounter a number of larger transactions which effect a lot of rows? For example an update statement which updates 100,000...

Your understanding is correct. It is also possible to tune the agent by adjusting different profile parameters. This is especially useful on high transaction databases. The key...

But the commands appear to be delivered rapidly?

If so there would appear to be a bottleneck with your logreader as this is where the trace flags are read...

We always use the none option but the principle is the same. As you are not changing the subscribers they will require no changes so long as you are...

I should say, there's a 2k5 version too.

**Highlander quote** - "There can be only one."

Because there is only really one useful one.

http://www.amazon.co.uk/Server-2008-Replication-Experts-Voice/dp/143021807X/ref=sr_1_1?ie=UTF8&qid=1300907920&sr=8-1

Assuming the publisher data isnt going to change you can resetup the replication as a 'nosync' subscription.

When using the sp_addsubscription proc to readd the subscriber set the @sync_type to 'none'...

Its possible there is a single large transaction being copied between servers. Alternatively, is there any contention being shown on the subscriber? Can you see commands being applied...

Depending on the cause and the size of the table you could use tablediff.exe.

Usually here.

C:\Program Files\Microsoft SQL Server\90\COM\tablediff.exe

Or don't follow microsofts poor example of using reserved words for column names!

Best practices? I think not. 😀