Showing posts with label allis. Show all posts
Showing posts with label allis. Show all posts

Friday, March 23, 2012

Rebuilding indexes in SQL 2000

All
Is there any way to estimate how long it would take to drop and rebuild the
indexes on a database. I have a farily tight maintenance window on a payroll
database and need to be sure that any work would be completed in time. I
assume the database size and amount of tables has a major bearing but not
sure where I would go from that info.
Thanks
Si
Simon
You can determine what tables are heavely defragmented and run rebuilt
index only on them
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:5D6C2F49-E817-4E24-893A-B108549F5331@.microsoft.com...
> All
> Is there any way to estimate how long it would take to drop and rebuild
> the
> indexes on a database. I have a farily tight maintenance window on a
> payroll
> database and need to be sure that any work would be completed in time. I
> assume the database size and amount of tables has a major bearing but not
> sure where I would go from that info.
> Thanks
> Si
|||On Feb 27, 9:37 am, Simon <S...@.discussions.microsoft.com> wrote:
> All
> Is there any way to estimate how long it would take to drop and rebuild the
> indexes on a database. I have a farily tight maintenance window on a payroll
> database and need to be sure that any work would be completed in time. I
> assume the database size and amount of tables has a major bearing but not
> sure where I would go from that info.
> Thanks
> Si
Rather than rebuild ALL of the indexes, consider rebuilding only those
that are badly fragmented. Rebuilding all of them is usually
unnecessary. Here's a script that might help you:
http://realsqlguy.blogspot.com/2007/02/smart-index-defragmentation.html
|||Simon,
there are too many variables in your case for an estimation from someone
external to work.
You could generate your own decent estimate if you restore a recent backup
onto a test server of similar specs and run the rebuild there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||The problem I have is the database has around 600 tables, of which 350 need
rebuilding. There is also a high level of fragmentation so I thought that
Reindexing would be quicker.
"Tracy McKibben" wrote:

> On Feb 27, 9:37 am, Simon <S...@.discussions.microsoft.com> wrote:
> Rather than rebuild ALL of the indexes, consider rebuilding only those
> that are badly fragmented. Rebuilding all of them is usually
> unnecessary. Here's a script that might help you:
> http://realsqlguy.blogspot.com/2007/02/smart-index-defragmentation.html
>

Rebuilding indexes in SQL 2000

All
Is there any way to estimate how long it would take to drop and rebuild the
indexes on a database. I have a farily tight maintenance window on a payroll
database and need to be sure that any work would be completed in time. I
assume the database size and amount of tables has a major bearing but not
sure where I would go from that info.
Thanks
SiSimon
You can determine what tables are heavely defragmented and run rebuilt
index only on them
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:5D6C2F49-E817-4E24-893A-B108549F5331@.microsoft.com...
> All
> Is there any way to estimate how long it would take to drop and rebuild
> the
> indexes on a database. I have a farily tight maintenance window on a
> payroll
> database and need to be sure that any work would be completed in time. I
> assume the database size and amount of tables has a major bearing but not
> sure where I would go from that info.
> Thanks
> Si|||On Feb 27, 9:37 am, Simon <S...@.discussions.microsoft.com> wrote:
> All
> Is there any way to estimate how long it would take to drop and rebuild th
e
> indexes on a database. I have a farily tight maintenance window on a payro
ll
> database and need to be sure that any work would be completed in time. I
> assume the database size and amount of tables has a major bearing but not
> sure where I would go from that info.
> Thanks
> Si
Rather than rebuild ALL of the indexes, consider rebuilding only those
that are badly fragmented. Rebuilding all of them is usually
unnecessary. Here's a script that might help you:
http://realsqlguy.blogspot.com/2007...gmentation.html|||Simon,
there are too many variables in your case for an estimation from someone
external to work.
You could generate your own decent estimate if you restore a recent backup
onto a test server of similar specs and run the rebuild there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||The problem I have is the database has around 600 tables, of which 350 need
rebuilding. There is also a high level of fragmentation so I thought that
Reindexing would be quicker.
"Tracy McKibben" wrote:

> On Feb 27, 9:37 am, Simon <S...@.discussions.microsoft.com> wrote:
> Rather than rebuild ALL of the indexes, consider rebuilding only those
> that are badly fragmented. Rebuilding all of them is usually
> unnecessary. Here's a script that might help you:
> http://realsqlguy.blogspot.com/2007...gmentation.html
>sql