Thanks Scott, that's kind of what I thought might happen but wanted confirmation. I know if the size was "reduced" it would cause that to happen, but wasn't sure...

Can what run? The actual shrink process or the rollback?

The shrink process can take days depending on how much you're attempting to shrink at a time...the rollback should be...

Killing it won't do any harm whatsoever. It shouldn't take long at all to rollback and it's only doing small chunks behind the scenes

Another note: If SQL 2008 or lower, the shrink process is single-threaded = takes forever.

Despite the obvious fragmentation you're going to cause, you could try shrinking at a smaller chunk,...

Just a shot, but try temporarily disabling the triggers to see if the issue goes away. And I'm curious, what do these triggers do?

I've also seen situations where extremely long...

My preference is to: 1) Use a single log file per database 2) Ensure auto-growth settings are set to some reasonable amount in MB (not percentages) and 2) size the...

Perhaps a nested ForEach loop container - I'd think about creating a "delimiter" variable, then place a script inside the ForEach task, one that picks up the file, opens it,...

I think you need to set the trace event first:

EXEC sp_trace_setevent @TraceID, 13, 11, 1

EXEC sp_trace_setfilter @TraceID, 1, 11, 0, 0, N'joe';

Could be that someone is running a query against a table, which temporarily blocks the replication commands from being committed at the subscriber(s)

Your Tech Services /IT department needs to set up the server you are sending the email from to "relay" email to the exchange/mail server.

Not sure about the error you are receiving, but you can look at setting subscription streams to potentially get a performance boost - check out this article here: http://blogs.msdn.com/b/repltalk/archive/2010/03/01/navigating-sql-replication-subscriptionstreams-setting.aspx

This...

Again, 2 thousand commands is nothing to worry about, unless of course you are noticing that for a very long time (like it's still sending you those message after 5-10...

Are you absolutely 100% certain you're running this against the proper database and server?

FYI - no worries about having 2 publications, we have about a dozen over here, and about...

no rows? Run it when you know it's behind...

You can also try running:

distribution.dbo .sp_replmonitorhelpsubscription @publisher = 'SERVERNAME' , @publication_type = 0

And sp_replcounters

Also check...

Awesome, glad it worked.