I think I have it fixed, although I don't know the exact cause.
I used the Wizard to create the backup job for all databases. I decided to
break out the database that was having the problem into it's own job. Then,
I deleted the other (all) plan, and recreated it without including the
trouble database.
No problems last night. Who knows what will happen tonight, but I feel more
confident. Something must have become corrupt.
BTW, to answer the questions, this is SQL 2000 server. There was nothing in
the SQL log that would point to a problem.
Thanks!
Doug
"Simon Hayes" <sq*@hayes.ch> wrote in message
news:60**************************@posting.google.c om...
"Doug" <dg*****@hotmail.com> wrote in message
news:<9q******************@newssvr31.news.prodigy. com>...
Hello. Have a strange one here. I'm backing up databases locally to a
drive on the server daily. I needed to change the time of the backup, and did
that, but it's still occuring at the old time.
I deleted the old job, and recreated it with the new time. I won't know
until tonight at 12:00 whether that worked or not.
Can someone tell me where it saves the maintenance schedules and how it
kicks it off? I'd like to take a look at it to see if it's still there.
I'm a little bit of a newbie on SQL server, so be gentle. :-)
Can you give some more information on exactly what you did (and which
version of SQL Server you're using)? It looks like you're using the
maintenance plan wizard - which databases did you choose to backup,
what time did you select for the backups, what time are they actually
running at, what happens if you schedule a BACKUP command in a
scheduled job instead of using the wizard etc. And is there anything
relevant in the SQL Server Agent log?
Simon
