The same topic goes on http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=259826

Are you guys running queries with (nolock) clause or after in read uncommitted transaction isolation level? If this is the case, then no wonder - this is by design, just...

The big question is: Who is the distributor?

Usually, the distributor is the same as the publisher, this is the default. In this case...

Steve,

If you have continuous replication, set up an additional schedule for the distribution agent. Set it to run in every 5 minutes. This way, in case of the replication job...

Hi,

These were my thoughts, I do like separating SQL data from OS totally and I don't believe in separating indexes from table data. Many people think the opposite.

As I saw...

Hi,

First of all, if you're new to replication, I suggest you to read the first few chapters from SQL BOL (Books Online). It's really worth it.

Do you mean the distribution...

Hi Mindy,

When we had similar problem, we must have disabled the logging at the ODBC connection, and after that we could read the log file. Give it a try...

Hi,

Some thoughts:

1. I wouldn't put the system databases (basically any dbs) to the OS partition. I'd put them next to the distribution and other small dbs.

2. Blocking in itself is...

Hi,

You have two choices:

1. Use the WITH (NOLOCK) clause mentioned above, this case you'll read out uncommitted transactions as well.

2. Use the WITH (READPAST) clause, this case you'll skip the...

Hi,

This means that your distribution agents were blocked somehow. Either by each other or - which is more frequent at us - by the Logreader Agent. Check the distribution.dbo.msrepl_transactions table...