Hi, Yes you may find that details SQL Log

All, I do not like using the native sql server 2005 maintenance plans but rather script out tasks to perform maintenance. I do the following... Backup databases nightly (full) using Redgate. 15 minute t-log backups using Redgate. Defrag any index greater than 30% fragmentation rate every night (the logs...

I have 2 questions 1) One big index performs better then 2 small indexes or the opposite? 2) I have table with 17242772 rows and I have index1 and index2 on that table, index1 has 14 columns and index2 has 3 columns. Developer created a new report in crystal it takes 2:47 min. I analyze the query through...

Fair enough, but when you talk about re-organisation that tends to be for data too and handling such a volume needs to have normalization in order to retain the performance on adhoc basis. [quote user="Adriaan"] Satya, I was just bringing up the point of reorganization as a tool of the consultancy...

See notes from BOL: Specifies the index leaf level will be reorganized. This clause is equivalent to the older DBCC INDEXDEFRAG. ALTER INDEX REORGANIZE statement is always performed online. This means long-term blocking table locks are not held and queries or updates to the underlying table can continue...

Have you tried to see whats happening using server side trace in this case? Article on the rebuilding index tips, if you haven't found nothing from the logs it may be better to seperate the SHRINK operation with another script rather than joining them with reindex one.