Viewing 15 posts - 1,546 through 1,560 (of 5,103 total)
this is a common thing because those jobs that generate a lot of transaction log records create a big contention for replication stored procedures. You could stop the Log reader...
* Noel
October 1, 2007 at 3:23 pm
... I am not sure how this procedure, sp_scriptdynamicupdateproc , is used, it won't parse for me ...
Why are you saying that it won't parse ? Is this happening when...
* Noel
October 1, 2007 at 3:21 pm
hawg (10/1/2007)
* Noel
October 1, 2007 at 3:04 pm
A very important part of monitoring is to setup a BASELINE so that you "know" your system workload effects under "normal" conditions.
* Noel
October 1, 2007 at 2:52 pm
mjschwenger (9/30/2007)
Please, note that the slow statement is the one that uses bind parameters, not literals....
* Noel
October 1, 2007 at 2:47 pm
select * from sys.dm_exec_sessions -- 2005 style 😉
* Noel
October 1, 2007 at 2:28 pm
May I suggest you NEVER, EVER use EM nor SSMS for DDL ? You want to be in control of what is actually going to happen. It does not take...
* Noel
October 1, 2007 at 12:28 pm
When you add a new column it does takes time to go through the pages locking people (connections) out allocating / splitting pages for the column space and updating all...
* Noel
October 1, 2007 at 12:24 pm
you run Profiler traces on an SQL Server 2005 with 2005 profiler client tool. By default it reads in microseconds and displays in milliseconds. You can change the display to...
* Noel
October 1, 2007 at 11:21 am
Actually microsecond tunning is the as millisecond tunning the actual thing is that previously a very large amount of very low duration queries would escape under the radar and now...
* Noel
October 1, 2007 at 11:14 am
glad to help
* Noel
October 1, 2007 at 11:09 am
October 1, 2007 at 11:08 am
Viewing 15 posts - 1,546 through 1,560 (of 5,103 total)