I have a couple of questions regarding setting up a maintenance plan in 2008 (Standard Edition).
1. When you are setting up a Rebuild Index task you have an option to "Sort Results in tempdb" as well as "keep index online while reindexing"
I have to scenarios which I would appreciate some direction of the pro's / con's on what would be recommended for these settings.
SQL 2005 / 2008 Std. install with separate drives for mdf (i.e. E:\) and ldf files (i.e. F:\) which have the system db's on the same drives
1-3 gb's of RAM and RAID 5 disc configuration
I am pretty sure you cannot (based on what i found on BOL), but I will ask to be 100% clear. Can you enable 'keep index online while reindexing' for a standard version of 2005 / 2008? I have read that it is only for Dev / Enterprise editions.
if that is true and it is only for advanced editions, why is it an option in the standard edition menu?
what happens if you enable it? does it just Not work?
SQL 2008 Enterprise server with 16 gb's ram with separate drives for system databases as well as multiple drives (6 to 8) for user database with a 1 data file per drive configuration RAID 5 configuration
Database sizes vary between 200 gb to 500gb
what would be the best or most recommended method of maintaining databases of this size?
Run with a maintenance plan wizard type setup? or find a custom script to maintain databases of this size?
I have seen posts where people run the "keep index online while reindexing' and the process takes an extremely long time 10-20 hours???
Lastly, is there any combination of the settings that either enhance / hinder / cancel out performance based on the above scenarios?
Thanks in advance for any experiences or recommendations.