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...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
by
on
Fri, Apr 25 2008
Filed under:
Filed under: sql server, indexes, memory, databases, cache, cpu, monitoring, operating system, huge, dbcc shrinkfile