Chiming in at Gail's request...

There's no way to detect corrupt statistics. The statistics blobs are not checked by DBCC CHECKDB as the query optimizer team has never provided a mechanism...

NP - here to help.

Indeed. The log file metadata will only be updated when it grows or shrinks - possibly when the file header page at the front is updated after a backup, log...

The log is usually circular in nature so overwrites itself and doesn't need to grow. Checkout the article for full details.

This isn't a problem. Your log will only grow if it needs to - not growing is a good thing.

See this article I wrote for TechNet Magazine: Understanding Logging and...

And I meant to add, I use the index_usage_stats DMV all the time with clients - helps to see how indexes are being used, which can be more important than...

Invisible indexes - you can already do that in SQL Server since 2005 - ALTER INDEX .... DISABLE and then REBUILD to enable it again if you want.

If you do repair_allow_data_loss you will lose data from that table as the page is from the leaf level of the clustered index. I would recommend restoring using your backups...

You could save yourself the money of the tool and just rebuild the transaction log in EMERGENCY mode - you'll get the same transactional consistency on the data as from...

Nowadays I tend to recommend taking the backup, restoring it somewhere else and then running CHECKDB on the restored copy of the database. It checks that your database is corruption...

To answer a different interpretation of the question - no, people do not generally run CHECKDB before doing a nightly index rebuild.

How often should you run CHECKDB? It depends on...

These are errors in the statistics blobs for the database EPICSYS (some of their pages are marked as allocated in two IAM pages for two objects) and you're not going...

Dave Coats (8/5/2010)

---

Sounds like you just need to do a transaction log backup which will decrease the size of the log files. Do you have a regularly scheduled transaction...

Please continue the thread here where everyone can benefit from the discussion.

Could be that you have more memory on the 2008 server and checkpoint is occuring less frequently and the log is growing until checkpoint occurs and clears the log.

What does...