Viewing 15 posts - 166 through 180 (of 1,580 total)
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,...
July 18, 2014 at 12:01 pm
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...
June 18, 2014 at 10:28 pm
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...
June 18, 2014 at 1:46 pm
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,...
June 17, 2014 at 10:22 am
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';
June 16, 2014 at 5:29 pm
Could be that someone is running a query against a table, which temporarily blocks the replication commands from being committed at the subscriber(s)
June 11, 2014 at 1:40 pm
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.
June 11, 2014 at 9:27 am
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:
June 11, 2014 at 9:25 am
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...
June 11, 2014 at 8:53 am
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...
June 10, 2014 at 11:49 pm
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...
June 9, 2014 at 8:56 am
You need to determine possible causes of the high count... It could be you've got to much going on on the publisher/distributor (you infer that these are on the same...
June 8, 2014 at 8:15 am
Any chance you have a trigger on the table in one of the subscribers?
June 8, 2014 at 8:09 am
Yes, please review that article...and then upload your current execution plan. Just guessing, but you'll most like have a clustered index scan on T1 and T2 (unless it's a...
June 8, 2014 at 8:05 am
Viewing 15 posts - 166 through 180 (of 1,580 total)