Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 Maintenance Plan

Author  Topic 

kid_on_the_block
Posting Yak Master

172 Posts

Posted - 2006-03-09 : 22:28:41
Hi

As per my backup policy I need to do a full backup dialy & transactional backup every 30 minutes , can i use the Maintenance plan to do this

or should I write T-sql statements & create jobs.....

I mean whats the difference between the two methods.


Thanks


jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2006-03-09 : 22:37:29
write your own...

1. errors are easily discernible compared to maint plans
2. you can trace how things are basically done
3. you can modify the jobs and tsql when needed without recreating the entire setup

HTH

--------------------
keeping it simple...
Go to Top of Page

kid_on_the_block
Posting Yak Master

172 Posts

Posted - 2006-03-10 : 04:31:32
Thanks
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-03-10 : 09:45:34
"write your own..."

Use the maintenance plans

The maintenance plans have their problems, however writing a good, safe, reliable alternative takes time and plenty of "shaking down". It took us a lot of work before we were comfortable to replace Maintenance Plan with our own.

Up until then we ran Maintenance plan AND our own (clearly your own cannot ALSO do TLog backups, so we left Maintenance Plan doing that until we were sure we had the rest of ours correct - including deleting old files at the right time, and no earlier!)

Kristen
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2006-03-10 : 10:41:29
now me thinks Kristen is planning to extend this thread...

each to his own then eh? I did daily backups and crossed my fingers that nothing will happen until i've finished the jobs needed to assure me of a good DR process

personally, it's better you know why your job failed than trying to decipher what happened? this is similar to...

developer: i encountered an error
netadmin: ok
[after few minutes]
netadmin: can you retry now?
developer: it works ok now, what did you do?
netadmin: i restarted the server



--------------------
keeping it simple...
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-03-11 : 11:27:07
"it's better you know why your job failed than trying to decipher what happened"

Absolutely agree, but it does take some [elapsed] time & effort to shake down a good set of procedures.

Kristen
Go to Top of Page
   

- Advertisement -