January 23, 2013 at 7:45 am
runal_jagtap (1/23/2013)
Microsoft SQL Server 2005 - 9.00.5000.00 (X64)Dec 10 2010 10:38:40
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2
(Build 3790: Service Pack 2)
There is your problem, you have posted in a 2008 forum, so you got a 2008 answer, when you should of posted in the 2005 forum, or detailed from the start it was 2005.
The only way to rebuild a heap in 2005 is either pump data into a new table or create a clustered index then drop it, but would seriously recommend keeping the clustered index.
http://sqlblog.com/blogs/louis_davidson/archive/2008/02/26/2008-rebuilding-a-heap.aspx
January 23, 2013 at 7:49 am
runal_jagtap (1/23/2013)
TableNameIndexNameIndexTypePartitionNoNumRowsInTypeNumPagesTotKBsUsedKBsDataKBsTestHEAPHEAP11024112IN_ROW_DATA4465357203539235384
😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 23, 2013 at 7:50 am
I am totally :w00t: now
Will look in to this tomorrow.. thanks all for helping & assisting me
************************************
Every Dog has a Tail !!!!! :-D
January 23, 2013 at 9:00 am
Do not create then drop a clustered index. If you want a heap, live with the extent fragmentation. It's far less damaging than logical fragmentation. If you want to put a clustered index on, then put one on and leave it there.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply