Arthur Fuller
fuller.artful at gmail.com
Tue Nov 13 08:46:39 CST 2007
The physical size of the db is not of interest. The number of rows is the guideline here. A "re-organize pages" operation writes the entire db to tempdb and then creates a copy from tempdb and only when said copy is complete does it destroy the original and rename the new copy to the original name. Given the number of rows involved, did you expect this to happen quickly? A. On 11/13/07, jwcolby <jwcolby at colbyconsulting.com> wrote: > > I made the foolish mistake of asking SQL Server to compact a large (200GB) > file using "reorganize pages". This is a static table with about 40% > empty > space and I foolishly thought this might be a good thing to do. OK FINE, > I > WAS FOOLISH ALRIGHT! 8-( > > I started it last night about 6:00 pm and as of this morning at 9:17 AM it > is still chugging away. Does anyone know whether this will actually > finish > some day and further whether that someday will be today or next January? > Fast server, lots of memory, fast disk. LOTS of CPU activity (50% of two > cores). > > This is a database that I need to get some work done on. > > John W. Colby > Colby Consulting > www.ColbyConsulting.com > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >