February 6, 2010 at 9:56 am
Good afternoon everybody,
I'm a few hours away from a maintenance window where I plan to perform an Offline index rebuild on a heavily fragmented database. In the majorty of cases these indexes are associated with tables that contain almost 100,000 rows but certain tables are contain well over half a million rows.
Now, with a little bit of effort, we've coaxed the business to agree a one hour maintenance window in which I should rebuild as many of the indexes as possible. As I'm keen for this process to go as quickly and as smoothly as possible, is there any preparations I could do with the SQL cluster to ensure that this happens without any hiccups?
As the production database is configured in an SQL cluster and specific databases later configured using SQL mirroring to a remote site, could failing over the server (in other words, shutting down the SQL services one the active node and starting the services on the redundent node) ensure that system performance is optimal and no user connections cause deadlock issues with the database that we are attempting to optimise?
thanks in advance,
AA
February 6, 2010 at 6:27 pm
I can't answer your question directly, because I have no experience with offline rebuilds. What I might suggest though is that the downtime is a problem, you might want to look into whether reorganizations would be sufficient.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply