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...
The message on subject is self-explanatory where your disk subsystem is referring to SQL Server that it is unable to cope up the demand. Having AUTOGROW option enabled on a SQL Server database is a common setup that allows SQL Server automatically expands the database when additional space is required...
How do you define the terms "Performance Monitoring"? What is your baseline & benchmarks? Have you ever used PERFMON (SYSMON) & PROFILER for serious performance issues within your SQL Server environment? The answer may be not 'yes' for all the questions above, in general getting...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
12-19-2007
Filed under: dashboard, sql server, performance, databases, microsoft, security, blog, environment, best practice, backups, monitoring, baseline, benchmarking, downloads, performance monitoring
As a DBA you should now how locking works with tables and how best you can make use of indexing enhancements within SQL Server 2005 version. Until SQL 2000 there was a limited availability of documentation on the guidelines even in the Books online and most of the times we have to depend upon the web...