Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

SQL Server 2005 Ghost in the Machine Expand / Collapse
Author
Message
Posted Tuesday, November 18, 2008 6:57 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Monday, August 11, 2014 9:44 AM
Points: 770, Visits: 1,597
Robert, i had a similar problem once, Take a drastic measure, disable all the jobs and enable them one by one, see which job causes your SQL to freeze, then concentrate on that job to see what actually happens behind the scenes, else use a profiler to get a trace data and figure it out. :)
Post #604344
Posted Tuesday, November 18, 2008 6:59 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, August 8, 2014 3:25 AM
Points: 2,283, Visits: 781
are all the jobs running concurrently ? if so there is a hard limit on the number of threads that can be allocated to these jobs


details can be found at

http://support.microsoft.com/kb/306457

but in summary the initially configured limits are as follows

activescripting 10
cmdexec 10
distribution 100
log reader 25
merge 100
snapshot 100
tsql 20




MVDBA
Post #604345
Posted Tuesday, November 18, 2008 7:04 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, September 22, 2014 1:13 PM
Points: 39, Visits: 287
UPDATE... We took the server down and shipped it off to IBM. I will update once the test results come back.
Post #604352
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse