|
|
Posted by traceable1 on 03/10/06 16:29
Thanks for the input!
I run this job on the weekends in the evening, but we have several
other load jobs going on at the same time.
Of course I would not want a user to get this message, but like Joe
mentioned, it would be great if it could have low priority, but
continue to run.
What I think I'll try is Erland's recommendation to update my proc so I
can have it restart where it left off. Since the DBREINDEX requires
exclusive access, this will probably be my best bet. But it seems to
me that the DEFRAG also requires exclusive access, since the job is
running the DEFRAG when it's killed.
I actually have another version of this proc I use to run on instances
which have hundreds of databases and it stores the database name and
datetime of when the job ran successfully so it can pick up where it
left off if it fails. I'll just modify that one to do the same with
the tables.
I guess I should also analyze the fragmentation and adjust the storage
parameters to see if this will help.
Thank you so much!
Navigation:
[Reply to this message]
|