Showing posts with label scheduled. Show all posts
Showing posts with label scheduled. Show all posts

Tuesday, March 27, 2012

Backing up SQL databases

I am backing up three databases being used for a
inventory program. I have scheduled these databases to
be backed up at night using enterprise manager. If I
needed to restore any of these databases would I have to
restore all three? I do not back up transaction logs
because they do not need to restore to a specific point
(they could restore back to the previous night when the
databases were being backed up). Also do I have to
backup the other default databases that came with the SQl
2000 server in order to restore the three databases
specific to the inventory program?
> If I
> needed to restore any of these databases would I have to
> restore all three?
Technically, each database can be restored independently. However, your
inventory application might need the data in all three databases to be in
sync. It is probably safest to restore all three unless you know enough
about the app to be certain restoring a single database isn't a problem.

> Also do I have to
> backup the other default databases that came with the SQl
> 2000 server in order to restore the three databases
> specific to the inventory program?
You should backup the master and msdb system databases as part of your
backup plan. These system databases only need to be restored if they are
lost or corrupted. You don't need to restore them before your inventory
databases.
Hope this helps.
Dan Guzman
SQL Server MVP
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
> I am backing up three databases being used for a
> inventory program. I have scheduled these databases to
> be backed up at night using enterprise manager. If I
> needed to restore any of these databases would I have to
> restore all three? I do not back up transaction logs
> because they do not need to restore to a specific point
> (they could restore back to the previous night when the
> databases were being backed up). Also do I have to
> backup the other default databases that came with the SQl
> 2000 server in order to restore the three databases
> specific to the inventory program?
|||OK thanks. Most of that makes sense to me. However the
last part you said referring to the default
databases, "you don't need to restore them before the
inventory databases." Do you mean if I had to restore
the inventory databases I would not have to restore these
default databases? Also if these default databases
became corrupt like you said would they not be able to be
replaced without having a backup of them. I mean if they
are default databases do they ever change? Are they
(default databases) unique to my particular SQL server
installation and are needed inclusively to run my
inventory app?
Lastly if I backup these three databases at night at
separate times wihtin a couple of hours of each when no
one is accessing the inventory program at all would they
still be in sync if restored all at once. If not could I
schedule all three databases to be backed up at the same
time to the server hard drive(I later back the database
backup files to tape).
[vbcol=seagreen]
>--Original Message--
to
>Technically, each database can be restored
independently. However, your
>inventory application might need the data in all three
databases to be in
>sync. It is probably safest to restore all three unless
you know enough
>about the app to be certain restoring a single database
isn't a problem.[vbcol=seagreen]
SQl
>You should backup the master and msdb system databases
as part of your
>backup plan. These system databases only need to be
restored if they are
>lost or corrupted. You don't need to restore them
before your inventory
>databases.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Andy" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
to[vbcol=seagreen]
SQl
>
>.
>
|||Hi,
Answers to your queries:-
1. Do you mean if I had to restore the inventory databases I would not
have to restore these
default databases?
No need to restore the default (system) databases while restoring Inventory
databases. System database keeps tract of database, logins, backups , jobs
... information. But you need to backup and keep these datases in a safe
location, which will be helpful during a crash or corruption.
2. I mean if they are default databases do they ever change?
Yes, they will change. Especially MASTER and MSDB database.
Master database will change while you add a new database, add a new login,
change parameters ...
MSDB database will change when you add a new Job (task), operator, backup,
restore ....
SO it is necessory to restore these backup during problem sitation.
3. Are they (default databases) unique to my particular SQL server
installation and are needed inclusively to run my inventory app?
Uniqueness will be there. Because those databases store the Server name,
logins, system informations...
4. If not could I schedule all three databases to be backed up at the same
time to the server hard drive?
You could backup these databases simulateneosly or one by one. One by one
is also fine, Because changes to these database will happen only during the
above mentioned time (answer to my second question)
Thanks
Hari
MCDBA
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...[vbcol=seagreen]
> OK thanks. Most of that makes sense to me. However the
> last part you said referring to the default
> databases, "you don't need to restore them before the
> inventory databases." Do you mean if I had to restore
> the inventory databases I would not have to restore these
> default databases? Also if these default databases
> became corrupt like you said would they not be able to be
> replaced without having a backup of them. I mean if they
> are default databases do they ever change? Are they
> (default databases) unique to my particular SQL server
> installation and are needed inclusively to run my
> inventory app?
> Lastly if I backup these three databases at night at
> separate times wihtin a couple of hours of each when no
> one is accessing the inventory program at all would they
> still be in sync if restored all at once. If not could I
> schedule all three databases to be backed up at the same
> time to the server hard drive(I later back the database
> backup files to tape).
> to
> independently. However, your
> databases to be in
> you know enough
> isn't a problem.
> SQl
> as part of your
> restored if they are
> before your inventory
> message
> to
> SQl
|||>> Lastly if I backup these three databases at night at[vbcol=seagreen]
If there is no activity at night, you should not have a consistency problem.
However, if there's activity at night, and if a user adds/modifies data to
database A and B, but not to C, you might hit a consistency issue since the
backups of each database will end at different times. In this case, you
will need to backup the transaction logs and restore to a point-in-time for
all 3 databases to guarantee consistency (or at least close to it, since
there's still a chance a trx is committed on database A, but not yet on B
and C at that time).
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...
> OK thanks. Most of that makes sense to me. However the
> last part you said referring to the default
> databases, "you don't need to restore them before the
> inventory databases." Do you mean if I had to restore
> the inventory databases I would not have to restore these
> default databases? Also if these default databases
> became corrupt like you said would they not be able to be
> replaced without having a backup of them. I mean if they
> are default databases do they ever change? Are they
> (default databases) unique to my particular SQL server
> installation and are needed inclusively to run my
> inventory app?
> Lastly if I backup these three databases at night at
> separate times wihtin a couple of hours of each when no
> one is accessing the inventory program at all would they
> still be in sync if restored all at once. If not could I
> schedule all three databases to be backed up at the same
> time to the server hard drive(I later back the database
> backup files to tape).
>
|||Can I also schedule backup of nondefault databases(our
inventory program) simultaneously?
>--Original Message--
>Hi,
>Answers to your queries:-
>1. Do you mean if I had to restore the inventory
databases I would not
>have to restore these
>default databases?
>No need to restore the default (system) databases while
restoring Inventory
>databases. System database keeps tract of database,
logins, backups , jobs
>... information. But you need to backup and keep these
datases in a safe
>location, which will be helpful during a crash or
corruption.
>2. I mean if they are default databases do they ever
change?
>Yes, they will change. Especially MASTER and MSDB
database.
>Master database will change while you add a new database,
add a new login,
>change parameters ...
>MSDB database will change when you add a new Job (task),
operator, backup,
>restore ....
>SO it is necessory to restore these backup during problem
sitation.
>3. Are they (default databases) unique to my particular
SQL server
>installation and are needed inclusively to run my
inventory app?
> Uniqueness will be there. Because those databases
store the Server name,
>logins, system informations...
>
>4. If not could I schedule all three databases to be
backed up at the same
>time to the server hard drive?
> You could backup these databases simulateneosly or one
by one. One by one
>is also fine, Because changes to these database will
happen only during the
> above mentioned time (answer to my second question)
>Thanks
>Hari
>MCDBA
>
>"Andy" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...
these[vbcol=seagreen]
be[vbcol=seagreen]
they[vbcol=seagreen]
I[vbcol=seagreen]
unless[vbcol=seagreen]
to[vbcol=seagreen]
point[vbcol=seagreen]
the
>
>.
>

Backing up SQL Databases

Hello:
How do you change the scheduled database backups in SQL Server 2000?
We have a scheduled backup of a production database that is run once a day.
We need to change it to update once a week; however, no matter what we do, we
can't remove or edit the existing backup schedule.
In the SQL Server Backup dialog box, regardless of whether the Destination
is removed and/or a new one is created, or if the Schedule is changed, none
of these new settings are ever saved. Why is this? What am I missing to get
around this?
Thanks,
Troy
Check your SQL Server agent jobs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a day.
> We need to change it to update once a week; however, no matter what we do, we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed, none
> of these new settings are ever saved. Why is this? What am I missing to get
> around this?
> Thanks,
> Troy
|||Hello,
Do you have enough previlages to update the job. Try login as SA and update
the job schedule using enterprise manager...
Thanks
Hari
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a
> day.
> We need to change it to update once a week; however, no matter what we do,
> we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed,
> none
> of these new settings are ever saved. Why is this? What am I missing to
> get
> around this?
> Thanks,
> Troy
|||Hello:
I am logged in under the SA account and trying to update the job in
enterprise manager. Is there something else I should be looking at or
resetting?
Thanks,
STroy
"Hari Prasad" wrote:

> Hello,
> Do you have enough previlages to update the job. Try login as SA and update
> the job schedule using enterprise manager...
> Thanks
> Hari
> "STroy" <STroy@.discussions.microsoft.com> wrote in message
> news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
>
>

Backing up SQL Databases

Hello:
How do you change the scheduled database backups in SQL Server 2000?
We have a scheduled backup of a production database that is run once a day.
We need to change it to update once a week; however, no matter what we do, we
can't remove or edit the existing backup schedule.
In the SQL Server Backup dialog box, regardless of whether the Destination
is removed and/or a new one is created, or if the Schedule is changed, none
of these new settings are ever saved. Why is this? What am I missing to get
around this?
Thanks,
TroyCheck your SQL Server agent jobs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a day.
> We need to change it to update once a week; however, no matter what we do, we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed, none
> of these new settings are ever saved. Why is this? What am I missing to get
> around this?
> Thanks,
> Troy|||Hello,
Do you have enough previlages to update the job. Try login as SA and update
the job schedule using enterprise manager...
Thanks
Hari
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a
> day.
> We need to change it to update once a week; however, no matter what we do,
> we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed,
> none
> of these new settings are ever saved. Why is this? What am I missing to
> get
> around this?
> Thanks,
> Troy|||Hello:
I am logged in under the SA account and trying to update the job in
enterprise manager. Is there something else I should be looking at or
resetting?
Thanks,
STroy
"Hari Prasad" wrote:
> Hello,
> Do you have enough previlages to update the job. Try login as SA and update
> the job schedule using enterprise manager...
> Thanks
> Hari
> "STroy" <STroy@.discussions.microsoft.com> wrote in message
> news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> > Hello:
> >
> > How do you change the scheduled database backups in SQL Server 2000?
> >
> > We have a scheduled backup of a production database that is run once a
> > day.
> > We need to change it to update once a week; however, no matter what we do,
> > we
> > can't remove or edit the existing backup schedule.
> >
> > In the SQL Server Backup dialog box, regardless of whether the Destination
> > is removed and/or a new one is created, or if the Schedule is changed,
> > none
> > of these new settings are ever saved. Why is this? What am I missing to
> > get
> > around this?
> >
> > Thanks,
> > Troy
>
>

Backing up SQL databases

I am backing up three databases being used for a
inventory program. I have scheduled these databases to
be backed up at night using enterprise manager. If I
needed to restore any of these databases would I have to
restore all three? I do not back up transaction logs
because they do not need to restore to a specific point
(they could restore back to the previous night when the
databases were being backed up). Also do I have to
backup the other default databases that came with the SQl
2000 server in order to restore the three databases
specific to the inventory program?> If I
> needed to restore any of these databases would I have to
> restore all three?
Technically, each database can be restored independently. However, your
inventory application might need the data in all three databases to be in
sync. It is probably safest to restore all three unless you know enough
about the app to be certain restoring a single database isn't a problem.
> Also do I have to
> backup the other default databases that came with the SQl
> 2000 server in order to restore the three databases
> specific to the inventory program?
You should backup the master and msdb system databases as part of your
backup plan. These system databases only need to be restored if they are
lost or corrupted. You don't need to restore them before your inventory
databases.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
> I am backing up three databases being used for a
> inventory program. I have scheduled these databases to
> be backed up at night using enterprise manager. If I
> needed to restore any of these databases would I have to
> restore all three? I do not back up transaction logs
> because they do not need to restore to a specific point
> (they could restore back to the previous night when the
> databases were being backed up). Also do I have to
> backup the other default databases that came with the SQl
> 2000 server in order to restore the three databases
> specific to the inventory program?|||OK thanks. Most of that makes sense to me. However the
last part you said referring to the default
databases, "you don't need to restore them before the
inventory databases." Do you mean if I had to restore
the inventory databases I would not have to restore these
default databases? Also if these default databases
became corrupt like you said would they not be able to be
replaced without having a backup of them. I mean if they
are default databases do they ever change? Are they
(default databases) unique to my particular SQL server
installation and are needed inclusively to run my
inventory app?
Lastly if I backup these three databases at night at
separate times wihtin a couple of hours of each when no
one is accessing the inventory program at all would they
still be in sync if restored all at once. If not could I
schedule all three databases to be backed up at the same
time to the server hard drive(I later back the database
backup files to tape).
>--Original Message--
>> needed to restore any of these databases would I have
to
>> restore all three?
>Technically, each database can be restored
independently. However, your
>inventory application might need the data in all three
databases to be in
>sync. It is probably safest to restore all three unless
you know enough
>about the app to be certain restoring a single database
isn't a problem.
>> Also do I have to
>> backup the other default databases that came with the
SQl
>> 2000 server in order to restore the three databases
>> specific to the inventory program?
>You should backup the master and msdb system databases
as part of your
>backup plan. These system databases only need to be
restored if they are
>lost or corrupted. You don't need to restore them
before your inventory
>databases.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Andy" <anonymous@.discussions.microsoft.com> wrote in
message
>news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
>> I am backing up three databases being used for a
>> inventory program. I have scheduled these databases to
>> be backed up at night using enterprise manager. If I
>> needed to restore any of these databases would I have
to
>> restore all three? I do not back up transaction logs
>> because they do not need to restore to a specific point
>> (they could restore back to the previous night when the
>> databases were being backed up). Also do I have to
>> backup the other default databases that came with the
SQl
>> 2000 server in order to restore the three databases
>> specific to the inventory program?
>
>.
>|||Hi,
Answers to your queries:-
1. Do you mean if I had to restore the inventory databases I would not
have to restore these
default databases?
No need to restore the default (system) databases while restoring Inventory
databases. System database keeps tract of database, logins, backups , jobs
... information. But you need to backup and keep these datases in a safe
location, which will be helpful during a crash or corruption.
2. I mean if they are default databases do they ever change?
Yes, they will change. Especially MASTER and MSDB database.
Master database will change while you add a new database, add a new login,
change parameters ...
MSDB database will change when you add a new Job (task), operator, backup,
restore ....
SO it is necessory to restore these backup during problem sitation.
3. Are they (default databases) unique to my particular SQL server
installation and are needed inclusively to run my inventory app?
Uniqueness will be there. Because those databases store the Server name,
logins, system informations...
4. If not could I schedule all three databases to be backed up at the same
time to the server hard drive?
You could backup these databases simulateneosly or one by one. One by one
is also fine, Because changes to these database will happen only during the
above mentioned time (answer to my second question)
Thanks
Hari
MCDBA
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...
> OK thanks. Most of that makes sense to me. However the
> last part you said referring to the default
> databases, "you don't need to restore them before the
> inventory databases." Do you mean if I had to restore
> the inventory databases I would not have to restore these
> default databases? Also if these default databases
> became corrupt like you said would they not be able to be
> replaced without having a backup of them. I mean if they
> are default databases do they ever change? Are they
> (default databases) unique to my particular SQL server
> installation and are needed inclusively to run my
> inventory app?
> Lastly if I backup these three databases at night at
> separate times wihtin a couple of hours of each when no
> one is accessing the inventory program at all would they
> still be in sync if restored all at once. If not could I
> schedule all three databases to be backed up at the same
> time to the server hard drive(I later back the database
> backup files to tape).
> >--Original Message--
> >> needed to restore any of these databases would I have
> to
> >> restore all three?
> >
> >Technically, each database can be restored
> independently. However, your
> >inventory application might need the data in all three
> databases to be in
> >sync. It is probably safest to restore all three unless
> you know enough
> >about the app to be certain restoring a single database
> isn't a problem.
> >
> >> Also do I have to
> >> backup the other default databases that came with the
> SQl
> >> 2000 server in order to restore the three databases
> >> specific to the inventory program?
> >
> >You should backup the master and msdb system databases
> as part of your
> >backup plan. These system databases only need to be
> restored if they are
> >lost or corrupted. You don't need to restore them
> before your inventory
> >databases.
> >
> >--
> >Hope this helps.
> >
> >Dan Guzman
> >SQL Server MVP
> >
> >"Andy" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
> >> I am backing up three databases being used for a
> >> inventory program. I have scheduled these databases to
> >> be backed up at night using enterprise manager. If I
> >> needed to restore any of these databases would I have
> to
> >> restore all three? I do not back up transaction logs
> >> because they do not need to restore to a specific point
> >> (they could restore back to the previous night when the
> >> databases were being backed up). Also do I have to
> >> backup the other default databases that came with the
> SQl
> >> 2000 server in order to restore the three databases
> >> specific to the inventory program?
> >
> >
> >.
> >|||>> Lastly if I backup these three databases at night at
>> separate times wihtin a couple of hours of each when no
>> one is accessing the inventory program at all would they
>>still be in sync if restored all at once.
If there is no activity at night, you should not have a consistency problem.
However, if there's activity at night, and if a user adds/modifies data to
database A and B, but not to C, you might hit a consistency issue since the
backups of each database will end at different times. In this case, you
will need to backup the transaction logs and restore to a point-in-time for
all 3 databases to guarantee consistency (or at least close to it, since
there's still a chance a trx is committed on database A, but not yet on B
and C at that time).
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...
> OK thanks. Most of that makes sense to me. However the
> last part you said referring to the default
> databases, "you don't need to restore them before the
> inventory databases." Do you mean if I had to restore
> the inventory databases I would not have to restore these
> default databases? Also if these default databases
> became corrupt like you said would they not be able to be
> replaced without having a backup of them. I mean if they
> are default databases do they ever change? Are they
> (default databases) unique to my particular SQL server
> installation and are needed inclusively to run my
> inventory app?
> Lastly if I backup these three databases at night at
> separate times wihtin a couple of hours of each when no
> one is accessing the inventory program at all would they
> still be in sync if restored all at once. If not could I
> schedule all three databases to be backed up at the same
> time to the server hard drive(I later back the database
> backup files to tape).
>|||Can I also schedule backup of nondefault databases(our
inventory program) simultaneously?
>--Original Message--
>Hi,
>Answers to your queries:-
>1. Do you mean if I had to restore the inventory
databases I would not
>have to restore these
>default databases?
>No need to restore the default (system) databases while
restoring Inventory
>databases. System database keeps tract of database,
logins, backups , jobs
>... information. But you need to backup and keep these
datases in a safe
>location, which will be helpful during a crash or
corruption.
>2. I mean if they are default databases do they ever
change?
>Yes, they will change. Especially MASTER and MSDB
database.
>Master database will change while you add a new database,
add a new login,
>change parameters ...
>MSDB database will change when you add a new Job (task),
operator, backup,
>restore ....
>SO it is necessory to restore these backup during problem
sitation.
>3. Are they (default databases) unique to my particular
SQL server
>installation and are needed inclusively to run my
inventory app?
> Uniqueness will be there. Because those databases
store the Server name,
>logins, system informations...
>
>4. If not could I schedule all three databases to be
backed up at the same
>time to the server hard drive?
> You could backup these databases simulateneosly or one
by one. One by one
>is also fine, Because changes to these database will
happen only during the
> above mentioned time (answer to my second question)
>Thanks
>Hari
>MCDBA
>
>"Andy" <anonymous@.discussions.microsoft.com> wrote in
message
>news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...
>> OK thanks. Most of that makes sense to me. However the
>> last part you said referring to the default
>> databases, "you don't need to restore them before the
>> inventory databases." Do you mean if I had to restore
>> the inventory databases I would not have to restore
these
>> default databases? Also if these default databases
>> became corrupt like you said would they not be able to
be
>> replaced without having a backup of them. I mean if
they
>> are default databases do they ever change? Are they
>> (default databases) unique to my particular SQL server
>> installation and are needed inclusively to run my
>> inventory app?
>> Lastly if I backup these three databases at night at
>> separate times wihtin a couple of hours of each when no
>> one is accessing the inventory program at all would they
>> still be in sync if restored all at once. If not could
I
>> schedule all three databases to be backed up at the same
>> time to the server hard drive(I later back the database
>> backup files to tape).
>> >--Original Message--
>> >> needed to restore any of these databases would I have
>> to
>> >> restore all three?
>> >
>> >Technically, each database can be restored
>> independently. However, your
>> >inventory application might need the data in all three
>> databases to be in
>> >sync. It is probably safest to restore all three
unless
>> you know enough
>> >about the app to be certain restoring a single database
>> isn't a problem.
>> >
>> >> Also do I have to
>> >> backup the other default databases that came with the
>> SQl
>> >> 2000 server in order to restore the three databases
>> >> specific to the inventory program?
>> >
>> >You should backup the master and msdb system databases
>> as part of your
>> >backup plan. These system databases only need to be
>> restored if they are
>> >lost or corrupted. You don't need to restore them
>> before your inventory
>> >databases.
>> >
>> >--
>> >Hope this helps.
>> >
>> >Dan Guzman
>> >SQL Server MVP
>> >
>> >"Andy" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
>> >> I am backing up three databases being used for a
>> >> inventory program. I have scheduled these databases
to
>> >> be backed up at night using enterprise manager. If I
>> >> needed to restore any of these databases would I have
>> to
>> >> restore all three? I do not back up transaction logs
>> >> because they do not need to restore to a specific
point
>> >> (they could restore back to the previous night when
the
>> >> databases were being backed up). Also do I have to
>> >> backup the other default databases that came with the
>> SQl
>> >> 2000 server in order to restore the three databases
>> >> specific to the inventory program?
>> >
>> >
>> >.
>> >
>
>.
>sql

Backing up SQL databases

I am backing up three databases being used for a
inventory program. I have scheduled these databases to
be backed up at night using enterprise manager. If I
needed to restore any of these databases would I have to
restore all three? I do not back up transaction logs
because they do not need to restore to a specific point
(they could restore back to the previous night when the
databases were being backed up). Also do I have to
backup the other default databases that came with the SQl
2000 server in order to restore the three databases
specific to the inventory program?> If I
> needed to restore any of these databases would I have to
> restore all three?
Technically, each database can be restored independently. However, your
inventory application might need the data in all three databases to be in
sync. It is probably safest to restore all three unless you know enough
about the app to be certain restoring a single database isn't a problem.

> Also do I have to
> backup the other default databases that came with the SQl
> 2000 server in order to restore the three databases
> specific to the inventory program?
You should backup the master and msdb system databases as part of your
backup plan. These system databases only need to be restored if they are
lost or corrupted. You don't need to restore them before your inventory
databases.
Hope this helps.
Dan Guzman
SQL Server MVP
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
> I am backing up three databases being used for a
> inventory program. I have scheduled these databases to
> be backed up at night using enterprise manager. If I
> needed to restore any of these databases would I have to
> restore all three? I do not back up transaction logs
> because they do not need to restore to a specific point
> (they could restore back to the previous night when the
> databases were being backed up). Also do I have to
> backup the other default databases that came with the SQl
> 2000 server in order to restore the three databases
> specific to the inventory program?|||OK thanks. Most of that makes sense to me. However the
last part you said referring to the default
databases, "you don't need to restore them before the
inventory databases." Do you mean if I had to restore
the inventory databases I would not have to restore these
default databases? Also if these default databases
became corrupt like you said would they not be able to be
replaced without having a backup of them. I mean if they
are default databases do they ever change? Are they
(default databases) unique to my particular SQL server
installation and are needed inclusively to run my
inventory app?
Lastly if I backup these three databases at night at
separate times wihtin a couple of hours of each when no
one is accessing the inventory program at all would they
still be in sync if restored all at once. If not could I
schedule all three databases to be backed up at the same
time to the server hard drive(I later back the database
backup files to tape).

>--Original Message--
to[vbcol=seagreen]
>Technically, each database can be restored
independently. However, your
>inventory application might need the data in all three
databases to be in
>sync. It is probably safest to restore all three unless
you know enough
>about the app to be certain restoring a single database
isn't a problem.
>
SQl[vbcol=seagreen]
>You should backup the master and msdb system databases
as part of your
>backup plan. These system databases only need to be
restored if they are
>lost or corrupted. You don't need to restore them
before your inventory
>databases.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Andy" <anonymous@.discussions.microsoft.com> wrote in
message
>news:451701c4800c$cb3dbbc0$a301280a@.phx.gbl...
to[vbcol=seagreen]
SQl[vbcol=seagreen]
>
>.
>|||Hi,
Answers to your queries:-
1. Do you mean if I had to restore the inventory databases I would not
have to restore these
default databases?
No need to restore the default (system) databases while restoring Inventory
databases. System database keeps tract of database, logins, backups , jobs
... information. But you need to backup and keep these datases in a safe
location, which will be helpful during a crash or corruption.
2. I mean if they are default databases do they ever change?
Yes, they will change. Especially MASTER and MSDB database.
Master database will change while you add a new database, add a new login,
change parameters ...
MSDB database will change when you add a new Job (task), operator, backup,
restore ....
SO it is necessory to restore these backup during problem sitation.
3. Are they (default databases) unique to my particular SQL server
installation and are needed inclusively to run my inventory app?
Uniqueness will be there. Because those databases store the Server name,
logins, system informations...
4. If not could I schedule all three databases to be backed up at the same
time to the server hard drive?
You could backup these databases simulateneosly or one by one. One by one
is also fine, Because changes to these database will happen only during the
above mentioned time (answer to my second question)
Thanks
Hari
MCDBA
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...[vbcol=seagreen]
> OK thanks. Most of that makes sense to me. However the
> last part you said referring to the default
> databases, "you don't need to restore them before the
> inventory databases." Do you mean if I had to restore
> the inventory databases I would not have to restore these
> default databases? Also if these default databases
> became corrupt like you said would they not be able to be
> replaced without having a backup of them. I mean if they
> are default databases do they ever change? Are they
> (default databases) unique to my particular SQL server
> installation and are needed inclusively to run my
> inventory app?
> Lastly if I backup these three databases at night at
> separate times wihtin a couple of hours of each when no
> one is accessing the inventory program at all would they
> still be in sync if restored all at once. If not could I
> schedule all three databases to be backed up at the same
> time to the server hard drive(I later back the database
> backup files to tape).
>
> to
> independently. However, your
> databases to be in
> you know enough
> isn't a problem.
> SQl
> as part of your
> restored if they are
> before your inventory
> message
> to
> SQl|||>> Lastly if I backup these three databases at night at
If there is no activity at night, you should not have a consistency problem.
However, if there's activity at night, and if a user adds/modifies data to
database A and B, but not to C, you might hit a consistency issue since the
backups of each database will end at different times. In this case, you
will need to backup the transaction logs and restore to a point-in-time for
all 3 databases to guarantee consistency (or at least close to it, since
there's still a chance a trx is committed on database A, but not yet on B
and C at that time).
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...[vbcol=seagreen]
> OK thanks. Most of that makes sense to me. However the
> last part you said referring to the default
> databases, "you don't need to restore them before the
> inventory databases." Do you mean if I had to restore
> the inventory databases I would not have to restore these
> default databases? Also if these default databases
> became corrupt like you said would they not be able to be
> replaced without having a backup of them. I mean if they
> are default databases do they ever change? Are they
> (default databases) unique to my particular SQL server
> installation and are needed inclusively to run my
> inventory app?
> Lastly if I backup these three databases at night at
> separate times wihtin a couple of hours of each when no
> one is accessing the inventory program at all would they
> still be in sync if restored all at once. If not could I
> schedule all three databases to be backed up at the same
> time to the server hard drive(I later back the database
> backup files to tape).
>|||Can I also schedule backup of nondefault databases(our
inventory program) simultaneously?
>--Original Message--
>Hi,
>Answers to your queries:-
>1. Do you mean if I had to restore the inventory
databases I would not
>have to restore these
>default databases?
>No need to restore the default (system) databases while
restoring Inventory
>databases. System database keeps tract of database,
logins, backups , jobs
>... information. But you need to backup and keep these
datases in a safe
>location, which will be helpful during a crash or
corruption.
>2. I mean if they are default databases do they ever
change?
>Yes, they will change. Especially MASTER and MSDB
database.
>Master database will change while you add a new database,
add a new login,
>change parameters ...
>MSDB database will change when you add a new Job (task),
operator, backup,
>restore ....
>SO it is necessory to restore these backup during problem
sitation.
>3. Are they (default databases) unique to my particular
SQL server
>installation and are needed inclusively to run my
inventory app?
> Uniqueness will be there. Because those databases
store the Server name,
>logins, system informations...
>
>4. If not could I schedule all three databases to be
backed up at the same
>time to the server hard drive?
> You could backup these databases simulateneosly or one
by one. One by one
>is also fine, Because changes to these database will
happen only during the
> above mentioned time (answer to my second question)
>Thanks
>Hari
>MCDBA
>
>"Andy" <anonymous@.discussions.microsoft.com> wrote in
message
>news:4b1f01c4801a$65fef810$a401280a@.phx.gbl...
these[vbcol=seagreen]
be[vbcol=seagreen]
they[vbcol=seagreen]
I[vbcol=seagreen]
unless[vbcol=seagreen]
to[vbcol=seagreen]
point[vbcol=seagreen]
the[vbcol=seagreen]
>
>.
>

Backing up SQL Databases

Hello:
How do you change the scheduled database backups in SQL Server 2000?
We have a scheduled backup of a production database that is run once a day.
We need to change it to update once a week; however, no matter what we do, w
e
can't remove or edit the existing backup schedule.
In the SQL Server Backup dialog box, regardless of whether the Destination
is removed and/or a new one is created, or if the Schedule is changed, none
of these new settings are ever saved. Why is this? What am I missing to get
around this?
Thanks,
TroyCheck your SQL Server agent jobs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a day
.
> We need to change it to update once a week; however, no matter what we do,
we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed, non
e
> of these new settings are ever saved. Why is this? What am I missing to ge
t
> around this?
> Thanks,
> Troy|||Hello,
Do you have enough previlages to update the job. Try login as SA and update
the job schedule using enterprise manager...
Thanks
Hari
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a
> day.
> We need to change it to update once a week; however, no matter what we do,
> we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed,
> none
> of these new settings are ever saved. Why is this? What am I missing to
> get
> around this?
> Thanks,
> Troy|||Hello:
I am logged in under the SA account and trying to update the job in
enterprise manager. Is there something else I should be looking at or
resetting?
Thanks,
STroy
"Hari Prasad" wrote:

> Hello,
> Do you have enough previlages to update the job. Try login as SA and updat
e
> the job schedule using enterprise manager...
> Thanks
> Hari
> "STroy" <STroy@.discussions.microsoft.com> wrote in message
> news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
>
>