January 4, 2006 at 6:19 am
I receive the following msg resulting from a backup (occasionally): "increase the
maximum worker threads for the SQL Server. Or decrease the maximum number of databases to backup concurrently". The same exact job succeeds throughout the day (different schedule). It fails only under the midnight schedule of this job. It is a cluster server with 4 CPUs in each server. I do have 400 or so connections throughout the day. My threads are set to the default of 255. Suggestions? Should I try to run dbcc sqlperf(UMSSTATS) during the midnight backup? On this dbcc I am looking for "work queued" being more that 0 or 1 and idle workers should be close to the same number as num workers, correct?
thanks
January 4, 2006 at 7:43 am
Is it the job that is failing or the backup itself that is failing.
If it is the job, be aware that the default number of jobs that SQL Server can run simultaneously is only 20.
Check out this article on how to configure the value so that it is more than 20. Also note that you are recommended to schedule jobs such that you have no more than 60 running at any one time.
http://support.microsoft.com/?kbid=306457
Hope this helps.
January 4, 2006 at 7:59 am
No other job is running consequtively. It is the backup that is failing.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply