Browse by Tags

• blocking
• fragmentation
• kba
• locking
• loss
• performance
• process
• profiler
• SQL Server
• stored procedure
• table

• Did we have recent autogrow?

  I just read the question how to find out when autogrow in tempdb happened. And again I want to push for the default trace. The simple answer is that you already have this information available, just go and get it! (Unless you explicitly disabled the default Read More... Posted Thursday, June 19, 2008 11:51 PM from Tibor Karaszi | (Comments Off) Filed under: trace

• How to use a stored procedure to monitor traces in SQL Server 2005

  The following pages were recently modified. Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise Edition Notification Contents: New and Major Modifications How to use a stored procedure to monitor traces in SQL Server 2005 http://support.microsoft.com/kb/912914/en-US...( Read More... Posted Wednesday, September 05, 2007 2:39 AM from SSQA.net | (Comments Off) Filed under: SQL Server, profiler, trace, process, stored procedure, kba

• Table fragmentation, Index contention and locking issues to resolve

  Yet another important factors that every DBA needs to concerned about table & index fragmentation within their SQL Server environment. Refer to the a rticle about DetectTableFragmentation in both 2000 and 2005 version. Fragmentation occurs due to Read More... Posted Wednesday, August 01, 2007 12:31 AM from SSQA.net | (Comments Off) Filed under: SQL Server, performance, blocking, profiler, locking, trace, process, loss, fragmentation, table