SQL Server Retsarting -- sql server clustering

Linchi Shea
5/31/2006 9:13:02 AM

If you don't want to touch your app, increase the value for max worker
threads option with sp_configure. Check out the info on max worker threads in
BOL. Note that if you have not changed its value, the default setting depends
on the number of processors. To get rid of the deadlocks, set it to be equal
or greather than the max number of connections your app makes.

Linchi

[quoted text, click to view]

Linchi Shea
5/31/2006 9:17:02 AM

[quoted text, click to view]

By the way, I should say 'set it to be equal or greather than the max number
of connections the apps make'. The setting should accommodate all the
connections instead of just connections from a single app.

SQL Server automatically restarts because the cluster service could not
connect to the instance to check its status.

Linchi

[quoted text, click to view]

steveh
6/6/2006 3:24:02 AM

Thanks Linchi

I was reading this recently, do you have any feedback on it

"a single worker can service multiple users"
"you shouldn't increase max worker threads unless someone from Microsoft or
one of its partners has advised you to"
"things like DBCC SQLPERF(umsstats) should give a strong indication that you
are running out of workers before you even think about something like this.
Further, the fact that you're running out of workers doesn't necessarily mean
that you should increase max worker threads. "
"If you are truly running out of workers, it makes good sense to find out
why before you begin tweaking the system configuration."

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server clustering

sql server clustering : SQL Server Retsarting