dpulte@mclaneco.com (Dpulte) wrote in message news:<1af2daed.0401211504.1e09a050@posting.google.com>...
> Are there any basic rules of thumb for how much disk free space is
> needed to even attempt a reorg on a SQL Server 2000 database? I have
> a database which is about 35 GB, and the drive it is on has about 19
> GB free. Another drive on the same server has about 25 GB free. Do I
> need 35 GB of free space on the same drive in order to even attempt a
> reorg? Can the reorg use free space on both drives? Do I just need
> enough free space for the largest table in the database?
>
> Also, are there any known dangers running a reorg on a database which
> may fail if not enough free space is found?
>
> Best regards
> Don

sql@hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0401220021.153a7e97@posting.google.com>...
> dpulte@mclaneco.com (Dpulte) wrote in message news:<1af2daed.0401211504.1e09a050@posting.google.com>...
> > Are there any basic rules of thumb for how much disk free space is
> > needed to even attempt a reorg on a SQL Server 2000 database? I have
> > a database which is about 35 GB, and the drive it is on has about 19
> > GB free. Another drive on the same server has about 25 GB free. Do I
> > need 35 GB of free space on the same drive in order to even attempt a
> > reorg? Can the reorg use free space on both drives? Do I just need
> > enough free space for the largest table in the database?
> >
> > Also, are there any known dangers running a reorg on a database which
> > may fail if not enough free space is found?
> >
> > Best regards
> > Don
>
> I'm not sure what you mean by a 'reorg' - if you mean DBCC CHECKDB,
> then you can use WITH ESTIMATEONLY to find out how much tempdb space
> would be required.
>
> Simon

> Are there any basic rules of thumb for how much disk free space is
> needed to even attempt a reorg on a SQL Server 2000 database? I have
> a database which is about 35 GB, and the drive it is on has about 19
> GB free. Another drive on the same server has about 25 GB free. Do I
> need 35 GB of free space on the same drive in order to even attempt a
> reorg? Can the reorg use free space on both drives? Do I just need
> enough free space for the largest table in the database?

"Erland Sommarskog" <sommar@algonet.se> wrote in message
news:Xns947970074FF1Yazorman@127.0.0.1...
> Dpulte (dpulte@mclaneco.com) writes:
> > Are there any basic rules of thumb for how much disk free space is
> > needed to even attempt a reorg on a SQL Server 2000 database? I have
> > a database which is about 35 GB, and the drive it is on has about 19
> > GB free. Another drive on the same server has about 25 GB free. Do I
> > need 35 GB of free space on the same drive in order to even attempt a
> > reorg? Can the reorg use free space on both drives? Do I just need
> > enough free space for the largest table in the database?
>
> That depends on how full the database is. If all those 35 GB are filled
> with data, then DBREINDEX will cause an auto-grow of the database. But
> how much is a little difficult to tell.
>
> I have not verified this, but I have the impression that when you run
> DBREINDEX on a table which have, say, 1GB reserved with few unsed pages,
> the reorganisation will lead to a table that has 2GB reserved. I guess
> this is because new pages are allocated when the clustered index is
> rebuilt, and the original pages are retained in case you want to reindex
> again.

>
> So with some unluck you could fill up that disk.
>
> To use the other disk you would have to extend the file group.
>
>
>
> --
> Erland Sommarskog, SQL Server MVP, sommar@algonet.se
>
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

> "Erland Sommarskog" <sommar@algonet.se> wrote in message
> news:Xns947970074FF1Yazorman@127.0.0.1...
>> I have not verified this, but I have the impression that when you run
>> DBREINDEX on a table which have, say, 1GB reserved with few unsed pages,
>> the reorganisation will lead to a table that has 2GB reserved. I guess
>> this is because new pages are allocated when the clustered index is
>> rebuilt, and the original pages are retained in case you want to reindex
>> again.
>
> That depends on your fill factor. We have some tables with the fill
> factor set to 90% since they see very few if any inserts.
>
> We have others with a 50% fill factor that I"m sure would do exactly what
> you say.