Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
john.burns
Posting Yak Master
100 Posts |
 Posted - 2007-03-08 : 12:23:06
|
| If I break up by reindex operation into a few separate jobs.. any problem running them concurrently?thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-03-08 : 12:40:16
|
| DBCC DBREINDEX is a very expensive operation. It uses a lot of system resources. I would not run them concurrently unless you have a slow period at night or something where you can afford to really halt the system.Tara Kizer |
 |
|
|
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-03-08 : 13:17:56
|
| thanks |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-03-09 : 04:52:15
|
| Just in case it helps:We use Defrag, instead of Reindex, because it is uses less resources than Reindex (we still reindex "small" tables)We use DBCC SHOWCONTIG to locate tables that are fragmented, and only rebuild those.Short of that maybe doing tables "A-F" on Monday, "G-N" on Tuesday, etc. would spread-the-load?Kristen |
|
|
|
|
|
|
Quick Ques. on REINDEX