THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » DBCC   (RSS)
  • Finding When Someone Last Ran a DBCC

      The other day someone on Twitter asked how to find out when or who last ran a DBCC FREEPROCCACHE command on their SQL Server instance. Since this is not an unusual request I figured I would post a few examples of how to find DBCC commands or even many similar commands or events. If you had a regular or Extended Event trace going you could ...
    Posted to Andrew Kelly (Weblog) by Andrew Kelly on June 28, 2017
  • Memory leak occurs when you run DBCC CHECKDB against a database in SQL Server 2014 - fixed in SQL Server 2014 CU6

    Great news today! At the end of January it was a Connect item  (https://connect.microsoft.com/SQLServer/Feedback/Details/1090203) that described a possible memory leak on the SQL Server 2014. The details are as follow:  sys.dm_os_memory_clerks for type = MEMORYCLERK_SQLQUERYEXEC and sys.dm_os_memory_objects for type ...
    Posted to Damian Widera (Weblog) by Damian Widera on February 19, 2015
  • DBCC CHECKDB on VVLDB and latches (Or: My Pain is Your Gain)

      Does your CHECKDB hurt, Argenis? There is a classic blog series by Paul Randal [blog|twitter] called “CHECKDB From Every Angle” which is pretty much mandatory reading for anybody who’s even remotely considering going for the MCM certification, or its replacement (the Microsoft Certified Solutions Master: Data Platform – makes my ...
    Posted to Argenis Fernandez (Weblog) by Argenis on June 17, 2013
  • Printing SPID information along with DBCC output

    Today on the #sqlhelp hash tag on twitter, @sqlsponge asked, I am trying to loop through each active spid for dbcc inputbuffer. How can I print spid with inputbuffer output? My response was that he should use sp_whoIsActive, or at least query the DMVs/DMFs manually, since they're much easier to work with than DBCC. But there is, of course, a way ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on October 6, 2011
  • Geek City: Nonclustered Index Keys

    I recently received a question about the storage of nonclustered index keys. I am assuming you are aware of the fact that if your table has a clustered index, SQL Server uses the clustered index key (all of its columns, if it is a composite index) as a 'bookmark' in your nonclustered indexes,  to allow your nonclustered indexes to uniquely ...
    Posted to Kalen Delaney (Weblog) by Kalen Delaney on March 16, 2008
  • Geek City: DBCC's Hidden Snapshot

      I had a fantastic time at the SQL Server 2008 JumpStart last week in Redmond. Getting to spend a whole week learning new stuff from Kim and Paul was awesome! My favorite topic was one from Paul called ''DBCC CHECKDB Fundamentals in only 487 slides.'' Although I am still absorbing much of that information, it did remind me of a DBCC CHECKDB ...
    Posted to Kalen Delaney (Weblog) by Kalen Delaney on February 10, 2008
  • Geek City: Detecting Overflowing Columns

    SQL Server 2005 allows rows to include variable length columns which do not actually fit in the maximum row size of 8060 bytes. I previously posted about row-overflow columns, and discussed the maximum number of such columns that you could have in a single table. You can read that post here. Just recently I received another question that ...
    Posted to Kalen Delaney (Weblog) by Kalen Delaney on October 9, 2007
  • Geek City: Clearing a Single Plan from Cache

    Caching and reusing query plans is both a good thing and a bad thing. Saving costs of recompilation for a query that is run repeatedly can be a good thing. Using a cached plan that is not appropriate can be a very bad thing. What do you do if you have plans in cache that should not be there? SQL Server 2000 and 2005 provide a way to clear ...
    Posted to Kalen Delaney (Weblog) by Kalen Delaney on September 29, 2007
  • DBCC OPENTRAN() behavior

    I recently was bitten by some not so obvious behavior with DBCC OPENTRAN() that I would like to share.  Basically this command is supposed to show you the oldest open transaction within the specified database or the current one if none is specified. If you run the example below you can see the expected behavior. USE Tempdb ;GOCREATE TABLE ...
    Posted to Andrew Kelly (Weblog) by Andrew Kelly on September 25, 2007
Privacy Statement