UP_REBUILD_ALL_INDEXES

Hi David

Both methods produce the same result, so if you use Rebuild Indexes Maint Plan for DB Impresario then do not need to run Tessitura's proc. UP_REBUILD_ALL_INDEXES.

A couple of notes:

1.
As of now Tessitura's  proc. UP_REBUILD_ALL_INDEXES uses DBCC DBREINDEX which I think will be modified soon because (a quote): Microsoft recommends avoiding the use of DBCC DBREINDEX as this feature will be removed in a future version of SQL Server.

2.
In UP_REBUILD_ALL_INDEXES they apply a custom fillfactor=70% for several tables (like T_TRANSACTION) ; the Rebuild Indexes Maint Plan uses the fill factor value last specified for the index --so essentially preserves it, if you select "Reorganize pages with the default amount of free space". So, we are OK with the fillfactor  too. 

You can check this out the existing  fillfactor value by running for instance:

select name, fill_factor
from sys.indexes where OBJECT_id =OBJECT_id ('T_TRANSACTION')

Thanks,

Simon

sbasyuk@carnegiehall.org

Hi David

Both methods produce the same result, so if you use Rebuild Indexes Maint Plan for DB Impresario then do not need to run Tessitura's proc. UP_REBUILD_ALL_INDEXES.

A couple of notes:

1.
As of now Tessitura's  proc. UP_REBUILD_ALL_INDEXES uses DBCC DBREINDEX which I think will be modified soon because (a quote): Microsoft recommends avoiding the use of DBCC DBREINDEX as this feature will be removed in a future version of SQL Server.

2.
In UP_REBUILD_ALL_INDEXES they apply a custom fillfactor=70% for several tables (like T_TRANSACTION) ; the Rebuild Indexes Maint Plan uses the fill factor value last specified for the index --so essentially preserves it, if you select "Reorganize pages with the default amount of free space". So, we are OK with the fillfactor  too. 

You can check this out the existing  fillfactor value by running for instance:

select name, fill_factor
from sys.indexes where OBJECT_id =OBJECT_id ('T_TRANSACTION')

Thanks,

Simon

sbasyuk@carnegiehall.org