I submit this suggested solution for review. I created this because we cannot have downtime on this site(24/7), or scripts that slow the system down that run during peak business hours. Because I cannot do ReIndexing due to uptime, I went for second best namely Index defrag that will give a bit of a performance boost. The 2000 database was still very slow running on SQL Server2005. After this there was a huge improvement. Please take note that the IndexDefag syntax is still 2000. Convert this at your own discretion to 2005 format with alter index syntax. I further suggest that you implement this for all your databases and specify different times to spread the processor load. I trust this might solve someone's problem.
This Stored Procedure can only run at a specific time, between 2 and 4 in the morning. Keep in mind I am in South Africa so the US date format might be deferent. First create the table to contain the log data. Then the SP, but first run a couple of tries and debugging...good luck...
Kobus van der Walt
