When performing an update to the EMR/PM applications, all SQL jobs related to the MicroMD and MicromdDMSObjects databases are reverted. Due to performance degradations that occur when some of the jobs run, we are forced to reschedule the jobs for a different time For example:

1) The "MicroMD: Defragment Indexes (Process)" job will completely render a database unusable while it is running. We reschedule this job from the default time to 1:00AM). Once an upgrade is performed, all modifications

2) Because the normal MicroMD backup jobs do not compress the backups (and we need the backups to run on a different time schedule), we have setup our own Maintenance Plans within SQL. We then disable the default MicroMD backup jobs.

Once an upgrade is performed, the schedules are reset on all of the Index processing jobs and all of the default MicroMD backup jobs are re-enabled. This results in a staff member having to remember to go in and reset all of this information each time. For cases of VARs hosting many databases, this can be a very time consuming process. Also, if for any reason it is forgotten, significant problems will result the following day when these default jobs/schedules kick off.

It would be nice if the DBUpdate utility would prompt the user if they would like to reset all of the SQL jobs or not.