This is a very tricky question and hard to stick to 1 or few solutions as answer, it depends! Overall the say is if there isn’t any resource contention (from your pre-installation testing & analysis) and there is enough of each resource to go around, then there is usually no reason to set any restrictions...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-04-2008
Filed under: sql server, memory, maintenance plan, i/o, clustered, best practice, monitoring, resources, configuration, performance monitoring, contention
Continuing on the MAX WORKER THREADS topic from ThisBlog I have been asked about method of calculating the amount of system resources that will be used when the setting is increased to 500 from 255 (default). Well, as one of the best practices you must test the implications and usage in hiking such a...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
11-15-2007
Filed under: sql server, performance, microsoft, server, tuning, dbcc, system, best practice, testing, resources, sqlperf, max worker threads