In general it is not a best practice to perform SHRINK database operation on a production server, atleast regularly! Sometimes it may be compulsory to keep them sized in order to ensure the disk storage is not compromised for any sudden changes to databases ETL processes, coming to the point by design...
Here comes another Frequently Asked Question (FAQ) on the forums and Frequently Posted Blog (FPB) here about high cpu issues on the SQL Server 2000 instances. Looking at high cpu spiks and performace issues is a common problem in all SQL Server installations, handling this issue within SQL Server 2005...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
09-20-2007
Filed under: sql server, performance, databases, blogs, blocking, query, kba, cpu, execution plan, backups, resources, high cpu, FAQ