hm - interesting problem.

I'm assuming there are no errors in the distribution cleanup job history - only ideas I have are manually running the sp_MSdistribution_cleanup SP with the appropriate parameters...

What is the retention period configured for your distributor? And do you have immediate_sync set for your publications?

I'm assuming that you're facing the issue outlined here - http://blogs.msdn.com/b/chrissk/archive/2009/07/27/how-replication-setting-immediate-sync-may-cause-transactional-replication-distribution-database-growth.aspx

I don't know if I've understood your problem completely so let me know if I've gone off on a tangent.

We do the following in our environments:

- Backup and restore the...

Here's another way:

SELECT name as field FROM sys.tables FOR XML PATH(''),ROOT('fields');

You could enable logging for the agents (snapshot agent and distribution agent) and see if anything more verbose is logged which could help pinpoint the issue.

Follow the steps listed here...

And thanks for taking the time to post the solution - this is good stuff to know (for me at least :-))

One option is to do this:

SET @tableHTML = REPLACE(@tableHTML,'<td>','<td align="right">');

There might be a better way to do via the XML also - I don't know how to do that 😉

You can use Adam Machanic's sp_whoisactive script to detect blocking (this can be downloaded from here). Use this to check for activity on the server and dig deeper into any...

There are multiple varities of scripts available for this purpose - here's a sample:

DECLARE @sql nvarchar(max)= '';

DECLARE @tab TABLE(DBName sysname NOT NULL, ObjectName sysname NOT NULL,...

You cannot drop the PK for a replicated article - you'll have to remove the article from the publication (basically not replicate the article), make the changes and add it...

I don't think the double \ causes any issues.

Are you sure you have enough space on the drive? net helpmsg 112 shows the error...

One of my friend told me that you should only replicate tables and then run scripts of Sps,views,functions at both publisher and Subscriber.

My questions are as

Q No1:-what is...

Can you post the actual error message you are seeing in the log reader agent. "No replicated transactions available" could also mean that there is no activity on the publisher...

About the warning message - from what I remember the warning message comes up by default when you select to replicate views or SPs (i.e. there's no checking done to...

As Roy said - the preferred method would be to initialize via a backup. We ran into the same issues (timeouts, taking a very large time etc even though we...