MS SQL Server - Always the Worker Thread

Author

Always the Worker Thread

RomM

2005-12-30, 7:23 am

I received the following msg resulting from a backup: (partial) "increase the
maximum worker threads for the SQL Server SQLSRVR\SSDDWP_SQL2. Or decrease
the maximum number of databases to backup concurrently". There is a another
full backup at a different time of day on this server that succeeds. This
instance is on a cluster server. I do not receive this msg throughout the
day. I do have 400 or so connections throughout the day. My threads are set
to the default of 255. I have 4 CPUs in each server. How can I accommodate
this backup? Would the idea be to run the dbcc sqlperf(UMSSTATS) at the same
time the backup is occurring?

RomM

2005-12-30, 9:23 am

One other question on the dbcc sqlperf(UMSSTATS). So my "work queued" at 0
or 1 and idle workers should be close to the same number as num workers?

thanks

"RomM" wrote:

> I received the following msg resulting from a backup: (partial) "increase the
> maximum worker threads for the SQL Server SQLSRVR\SSDDWP_SQL2. Or decrease
> the maximum number of databases to backup concurrently". There is a another
> full backup at a different time of day on this server that succeeds. This
> instance is on a cluster server. I do not receive this msg throughout the
> day. I do have 400 or so connections throughout the day. My threads are set
> to the default of 255. I have 4 CPUs in each server. How can I accommodate
> this backup? Would the idea be to run the dbcc sqlperf(UMSSTATS) at the same
> time the backup is occurring?
>

Sponsored Links