|
Posted by Greg D. Moore \(Strider\) on 04/25/07 03:24
"Rico" <me@you.com> wrote in message news:8LvXh.9$_G.8@edtnps89...
> Thanks Erland,
>
> I don't have a problem creating the T-SQL commands, it's using the
> Enterprise Manager to do more than create dbs is where I get lost.
That's the problem with using EM.
BTW... the reason you're seeing the behavior you're seeing is that the
maintenance job takes the conservative approach and assumes that the most
recent backup HAS to succeed before it'll delete the older one.
So setting it to 22 hours or anything won't force it to delete the older
file until the new one is successfully created.
>
> I will give that a try (creating a back up job and scheduling)
>
> THanks!
> Rick
>
>
> "Erland Sommarskog" <esquel@sommarskog.se> wrote in message
> news:Xns991D5A7E496DYazorman@127.0.0.1...
>> Rico (me@you.com) writes:
>>> Thanks, but I should have mentioned that I'm using SQL 2000 and I'm not
>>> using T-SQL, just trying to create the Maintenance plan from the
>>> Enterprise Manager.
>>
>> From what you described, you should not use a maintenance plan. Just set
>> up
>> a scheduled job to run the BACKUP statement. You can do this from the
>> GUI where you backup databases, and select Schedule somewhere on a
>> button.
>> In the end you get a one-step job that has a BACKUP job.
>>
>> Then again, if you have any interest in acquiring basic DBA skills, you
>> should certainly learn to write basic BACKUP commands in T-SQL.
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>>
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
[Back to original message]
|