That is one of the downsides to the index maintenance plans in SQL Server. Most DBA's that I know use a more targeted approach that checks the fragmentation levels of...

I concur with Gail on this one. If you are trying to come up with a one time process to generate the delete statements to incorporate into some other type...

If the vCenter database that you refer to is a vmWare Virtual Center database, then there is no reason that you cannot run it in Simple Recovery mode. It is...

Putting the database into Simple Recovery mode breaks the log backup chain. Depending on what you are doing it for and assuming you are going to put it back to...

I would also recommend "Troubleshooting SQL Server: A Guide for the Accidental DBA" by Jonathan Kehayias and Ted Krueger.

SQL Server performance tuning is an art and not a science. Every situation is different and you have to use a wholistic approach. The first thing I like to start...

Thanks Gail.

Back in the days of SQL 2000, Lumigent Log Explorer came in handy on multiple occasions. Once it was a developer who had access to the database through a front...

I stand corrected and have removed the inaccurate post. Is it possible that technique worked in SQL 2000? I've confirmed exactly what you stated using a copy of the AdventureWorks2008R2...

251-254 are reserved and are not used as non-clustered index id's. Prior to SQL Server 2005, you could only have 249 non-clustered indexes per table. SQL 2000 uses an index...

Absolutely a NO, NO! Do not DETACH the database.

The ultimate irony of being an experienced production DBA is that you almost invariably work your way out of a position unless the company continues growth at a staggering pace.

You also see the 999 non-clustered indexes if you reference the legacy sysindexes compatibility view.

select * from sysindexes

where id = object_id('customer')

In my sample script, I get index ID values up...

In SQL 2008, you can have up to 999 non-clustered indexes. You can confirm that by reviewing the maximum number of nonclustered indexes per table from the following maximum capacity...

Here's a link to a previous post that you'll want to take a look at:

http://www.sqlservercentral.com/Forums/Topic1232926-2893-1.aspx#bm1233046

Gail Shaw's advice is spot on: "For recovery without data loss, take a...