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
Usage of Temporary tables or variables is a common scenario in SQL Server world, since SQL Server 2005 usage of TEMPDB references to the blog posts here: http://sqlserver-qa.net/blogs/tools/archive/2007/04/05/sql-server-index-optimization-best-practices.aspx , http://sqlserver-qa.net/blogs/tools/archive...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
01-17-2008
Filed under: sql server, performance, msdn, blocking, maintenance plan, tempdb, tablesample, best practice, monitoring, FAQ, benchmarking, table variable, temp tables