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...
Bottlenecks aka locking & blocking is a quite common scenario within a RDBMS platform, that too SQL Server is not an exception at all. With an access to shared resources causes bottlenecks and demands on shared resources cause poor response time and must be identified and tuned. Few root causes for...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
02-25-2008
Filed under: sql server, performance, memory, dba, i/o, disk, 2008, development, cpu, best practice, capture, resource governor
The system DMV sys.dm_os_schedulers is an useful DMV to find such as running tasks & active workers threads etc. This is required to monitor the system state is heavily loaded or not, in particular this view will help you identify if there is any CPU bottleneck in the SQL Server machine. SELECT scheduler_id...
Yes it does! Until yesterday even I was under impression that it will not use or cause any issues to the server. But think about performing the SHRINK operation of transaction log & database files on regular basis, say within a scheduled job or ongoing process. Further to my tests refer to this SSPFAQ...
By now you should have applied the Service Pack 4 on your SQL Server 2000 instances and you might come across the message within the SQL error log " SQL Server has encountered 5877 occurrence(s) of IO requests taking longer than 15 seconds to complete on file ". Though this is classed as an...