SQL Server Performance Forum – Threads Archive
Index Rebuilding and Table LockingI’m aware that if you drop and create a Clustered Index that there will be a lock put on the table. This makes sense. I’ve also read that when you use DBCC DBREINDEX that Shared locks are put on the table during the rebuild of the Nonclustered Indexes. My question is… would the following also put a shared lock on a table? Keep in mind that the original index was also Nonclustered. CREATE NONCLUSTERED INDEX MYINFO
ON TRANSLOG (T_MYINFO ASC)
FILLFACTOR = 75,PAD_INDEX,DROP_EXISTING
Hi, If i am not wrong for your case, you need to explicitly specify ONLINE while performing indexing.
Be great in act, as you have been in thought.
IIRC, the OFFLINE/ONLINE switches are available only in Enterprise edition…