Mountain Man
Thanks for the answer. Yes, SQL Server Agent is running. Every other
database is being backed up according to the plan.
I was hoping there was just one thing I missed with this database, but as I
say, I've checked the obvious (data recovery model, backup file names).
Do you advocate setting up a manual backup plan rather than using
Microsoft's Maintenance Plan wizard? The attraction of the wizard was that
it timestamped the files, and was basically quick to set up (there are 13
databases so far). I attended a 1-week DBA course and this seemed to be the
approved procedure. It's worked fine up to this point.
Cheers
Iain
"mountain man" <hobbit@southern_seaweed.com.op> wrote in message
news:iG*****************@news-server.bigpond.net.au...
"Iain Hosking" <ii*********************@thespamfreeweather.com.au > wrote
in message news:40***********************@titanium.syd.ntt.ne t.au... I am running a SQL Server 2000 installation with several databases. Each
database and log is backed-up using a maintenance plan.
The scheduled maintance plan for the latest database does not run, but
displays no error. There is no entry in the job history. The same thing
happens when I try to run the individual jobs from Enterprise Manager.
I've checked the database recovery model (full), the location of the
backup files (same as the other databases), and just about everything else I
can think of. The scheduled maintenance plan for every other database runs
as it should.
What am I missing?
Is SQL Agent service running? This service is required
to be running for the above automation.
Additionally, I would disassociate the backups and the
maintenance plans by creating each as separate tasks,
the former being far more critical than the latter.
Pete Brown
Winluck P/L
Falls Creek
Australia