Browse by Tags

• allocation
• best practice
• blocking
• data
• dbcc
• deadlock
• defrag
• extent
• i/o
• index
• indexes
• insert
• locking
• log
• loss
• performance
• process
• profiler
• security
• showcontig
• SQL Server
• table
• tempdb
• trace
• update statistics

• DBCC EXTENTINFO - unused pages in these extents (undocumented)

  When it comes to resolving table fragmentation, the basic checkout you perform is to run DBCC INDEXDEFRAG or even run DBCC DBREINDEX statements. As per the default configuraiton SQL Database Engine allocates a new extent to an allocation unit only when Read More... Posted Tuesday, September 04, 2007 10:45 PM from SSQA.net | (Comments Off) Filed under: SQL Server, performance, indexes, fragmentation, table, deadlock, i/o, insert, data, allocation, extent

• Rebuild some fragmented indexes - problem with Extent Scan Fragmentation value

  This was the question from SSP forums, I’m trying to rebuild few fragmented indexes on a table that is updated on regular basis. The “dbcc showcontig” gave this result: Table: 'Confidential' (999999999); index ID: 5, database ID: 5 LEAF level scan performed. Read More... Posted Friday, August 24, 2007 9:24 PM from SSQA.net | (Comments Off) Filed under: security, SQL Server, performance, fragmentation, table, dbcc, index, showcontig, defrag

• Update statistics causing negative performance

  Recently we have seen a negative performance for a query that is running against a 500GB size of database, where AUTO UPDATE STATISTICS is enabled and we perform weekly reindexing on this database. In addition to this I perform intermittent update statistics Read More... Posted Saturday, August 18, 2007 11:11 AM from SSQA.net | (Comments Off) Filed under: SQL Server, performance, update statistics, fragmentation, index, tempdb, log, best practice

• 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