I have been assigned the task of DBA for our company's
payroll system running on SQL server 2k. My question is
this - In the maintenance plan, database backups,
transaction backups, etc...under properties it is backing
up 'master', everything is fine. However, our database
is 'WFT' shouldn't the database be set to WFT instead
of 'master'? Or does master contain all databases? I just
want to be sure we are getting the proper backup. Also
the job has the No Truncate command which causes the
event 17055. Can this command be omitted and everything
still be OK?
Thanks in advance.
DarrylThe link here should help you
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/createdb/cm_8_des_03_378k.asp
I suggest making 2 maintenance plans. I would do one for your System
Databases and select All System Databases in the wizard. Then do another
for All User Databases. For Backups I also have the wizard put all backups
in their own subdirectories. This makes viewing easier and you can easily
see what is going on.
--
Jeff Duncan
MCDBA, MCSE+I
"Darryl" <anonymous@.discussions.microsoft.com> wrote in message
news:824801c431db$326c6560$a001280a@.phx.gbl...
> I have been assigned the task of DBA for our company's
> payroll system running on SQL server 2k. My question is
> this - In the maintenance plan, database backups,
> transaction backups, etc...under properties it is backing
> up 'master', everything is fine. However, our database
> is 'WFT' shouldn't the database be set to WFT instead
> of 'master'? Or does master contain all databases? I just
> want to be sure we are getting the proper backup. Also
> the job has the No Truncate command which causes the
> event 17055. Can this command be omitted and everything
> still be OK?
> Thanks in advance.
> Darryl|||Darryl,
this is a simplification, but a typical plan is to do a
full back up of each of your user databases once a day and
much more frequent transaction log backups (eg every 30
mins). The log backups should be truncated, apart from in
the case of the 'live' log for disaster recovery.
The system databases should also be backed up and their
frequency will depend on how often you add logins, jobs
etc, but perhaps you might start with once a day.
All of this could be done using maintenance plans. Some of
the alternative options are not available in maintenance
plans (eg differential backups), but for this strategy it
is OK.
In books on line (BOL) there are plenty of details
explaining the various posibilities and setup techniques
(see "Backing Up and Restoring Databases").
HTH
Paul Ibison|||in addition to the answers you have been given, might I suggest you ask your
company to put a little investment into training for you (I am assuming that
a payroll system is quite important?!)
--
--
Br,
Mark Broadbent
mcdba , mcse+i
============="Darryl" <anonymous@.discussions.microsoft.com> wrote in message
news:824801c431db$326c6560$a001280a@.phx.gbl...
> I have been assigned the task of DBA for our company's
> payroll system running on SQL server 2k. My question is
> this - In the maintenance plan, database backups,
> transaction backups, etc...under properties it is backing
> up 'master', everything is fine. However, our database
> is 'WFT' shouldn't the database be set to WFT instead
> of 'master'? Or does master contain all databases? I just
> want to be sure we are getting the proper backup. Also
> the job has the No Truncate command which causes the
> event 17055. Can this command be omitted and everything
> still be OK?
> Thanks in advance.
> Darryl
