backup database

Dear all,
I backup the master, msdb, and my database from sql server 2000 by the add a backup devices and backup all of these db into the backup devices..
Then it have one .bak file including the db's. Is it can restore by the sql server 2000 when i reinstall the windows server and sql 2000 server?
or can i restore it into a new hardware system with windows server and sql 2000server?
Hi;
This BAK file can be restored in the below scenarios:
1. Restore in the same SQL server with a different name.
2. Restore it in the SQL Server after installation of Windows and SQL Server
3. Restore it in a SQL server with the same database name in a new hardware
For all the above you can use "RESTORE database " command.
Note:
This BAK files can be used when there is a crash of database. Better copy
this BAK file to
a safe place preferably to a TAPE device.
Thanks
Hari
MCDBA
"ken" <anonymous@.discussions.microsoft.com> wrote in message
news:672AFD82-EF81-4080-96D2-6344C048DCA2@.microsoft.com...
> Dear all,
> I backup the master, msdb, and my database from sql server 2000 by the add
a backup devices and backup all of these db into the backup devices..
> Then it have one .bak file including the db's. Is it can restore by the
sql server 2000 when i reinstall the windows server and sql 2000 server?
> or can i restore it into a new hardware system with windows server and sql
2000server?
|||The SQL Server that you are restoring to has to have the same build number
as the one the backup came from.
This applies to the system databases, not the user databases.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||What is the build number?
If i reinstall the windows server as well as the sql server, will the build number become a new number?

backup database

Dear all,
I backup the master, msdb, and my database from sql server 2000 by the add a
backup devices and backup all of these db into the backup devices..
Then it have one .bak file including the db's. Is it can restore by the sql
server 2000 when i reinstall the windows server and sql 2000 server?
or can i restore it into a new hardware system with windows server and sql 2
000server?Hi;
This BAK file can be restored in the below scenarios:
1. Restore in the same SQL server with a different name.
2. Restore it in the SQL Server after installation of Windows and SQL Server
3. Restore it in a SQL server with the same database name in a new hardware
For all the above you can use "RESTORE database " command.
Note:
This BAK files can be used when there is a crash of database. Better copy
this BAK file to
a safe place preferably to a TAPE device.
Thanks
Hari
MCDBA
"ken" <anonymous@.discussions.microsoft.com> wrote in message
news:672AFD82-EF81-4080-96D2-6344C048DCA2@.microsoft.com...
> Dear all,
> I backup the master, msdb, and my database from sql server 2000 by the add
a backup devices and backup all of these db into the backup devices..
> Then it have one .bak file including the db's. Is it can restore by the
sql server 2000 when i reinstall the windows server and sql 2000 server?
> or can i restore it into a new hardware system with windows server and sql
2000server?|||The SQL Server that you are restoring to has to have the same build number
as the one the backup came from.
This applies to the system databases, not the user databases.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||What is the build number?
If i reinstall the windows server as well as the sql server, will the build
number become a new number?

Backup

We are running SQL Server 2000, SP3. Do we need to stop SQL service before
backing up all the database (master, msdb, etc.)?
Thanks.No, SQL Server has always allowed you to back up a database while the server
is running.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:#TVYkJfZDHA.4020@.tk2msftngp13.phx.gbl...
> We are running SQL Server 2000, SP3. Do we need to stop SQL service
before
> backing up all the database (master, msdb, etc.)?
> Thanks.
>|||Thank you, Kalen.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uaBGjNfZDHA.1280@.tk2msftngp13.phx.gbl...
> No, SQL Server has always allowed you to back up a database while the
server
> is running.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> news:#TVYkJfZDHA.4020@.tk2msftngp13.phx.gbl...
> > We are running SQL Server 2000, SP3. Do we need to stop SQL service
> before
> > backing up all the database (master, msdb, etc.)?
> >
> > Thanks.
> >
> >
>

Backing up the Master, Model and MSDB databases

Hi,
I am new to SQL 2000 Server and as far as I have read, it seems that I
should backup the Master, Model and MSDB databases.
However, Should I...
1.) Backup the transaction log as part of the maintenance plan?
2.) Reorganize data and index pages?
3.) Remove unused space from database files?
4.) Check database integrity and should I include or exclude indexes? If
indexes are included/excluded, should I check to Attempt to repair any minor
problems and should I perform these checks before doing backups?
5.) Create a folder for each database?
6.) Remove files older than the default of 4 weeks or should I extend the
period?
Lastly,
7.) Write history to the table msdb.dbo.sysdbmaintplan_history and should I
limit rows to 1k, 5k, 10k, 100k rows for this plan?
Thank You in advance,
Dave
Try to give an answer to all of your numbered qustions, but remember that:
a) Is a good practice make a backup of your system database whenever you've
done some action that updates them; so, regarding the master, for example,
any CREATE, ALTER or DROP statement will surely update it, and make a backup
is a good idea; regarding the MSDB, each create, alter or drop of some Job,
Alert, Operator or any SSIS implementation, etc. will update it; regarding
the model, if you modify it could be a good idea make a backup.
About your qustions:
1) No for master database (you CANNOT backup transaction log of the master
DB!), optional for MSDB and model (but this means you apply a recovery
strategy, and you should carefully consider the interval between each backup)
2) No for master, optional for msdb and model; Oops: you can reorganise just
indexes, not data, considering clustered indexes as indexes and not data...
3)NEVER !!!
4)No for master, optional for msdb and model
5) and 6) As you like.
Generally, the recovery strategy for the system databases differs from the
one adopted for User databases, and a strategy too "regular" could be not so
efficient (suppose you plan a weekly - ora dayly - strategy, but on Tuesday
(for example) some big migration or some big deployment produces a lot of
updates on your system databases: I suggest a backup as soon as possible,
because a crash before the nightly batches could mean an important loss.
Gilberto Zampatti
"Dave" wrote:

> Hi,
> I am new to SQL 2000 Server and as far as I have read, it seems that I
> should backup the Master, Model and MSDB databases.
> However, Should I...
> 1.) Backup the transaction log as part of the maintenance plan?
> 2.) Reorganize data and index pages?
> 3.) Remove unused space from database files?
> 4.) Check database integrity and should I include or exclude indexes? If
> indexes are included/excluded, should I check to Attempt to repair any minor
> problems and should I perform these checks before doing backups?
> 5.) Create a folder for each database?
> 6.) Remove files older than the default of 4 weeks or should I extend the
> period?
> Lastly,
> 7.) Write history to the table msdb.dbo.sysdbmaintplan_history and should I
> limit rows to 1k, 5k, 10k, 100k rows for this plan?
> Thank You in advance,
> Dave

Backing up the Master, Model and MSDB databases

Hi,
I am new to SQL 2000 Server and as far as I have read, it seems that I
should backup the Master, Model and MSDB databases.
However, Should I...
1.) Backup the transaction log as part of the maintenance plan?
2.) Reorganize data and index pages?
3.) Remove unused space from database files?
4.) Check database integrity and should I include or exclude indexes? If
indexes are included/excluded, should I check to Attempt to repair any minor
problems and should I perform these checks before doing backups?
5.) Create a folder for each database?
6.) Remove files older than the default of 4 weeks or should I extend the
period?
Lastly,
7.) Write history to the table msdb.dbo.sysdbmaintplan_history and should I
limit rows to 1k, 5k, 10k, 100k rows for this plan?
Thank You in advance,
DaveTry to give an answer to all of your numbered qustions, but remember that:
a) Is a good practice make a backup of your system database whenever you've
done some action that updates them; so, regarding the master, for example,
any CREATE, ALTER or DROP statement will surely update it, and make a backup
is a good idea; regarding the MSDB, each create, alter or drop of some Job,
Alert, Operator or any SSIS implementation, etc. will update it; regarding
the model, if you modify it could be a good idea make a backup.
About your qustions:
1) No for master database (you CANNOT backup transaction log of the master
DB!), optional for MSDB and model (but this means you apply a recovery
strategy, and you should carefully consider the interval between each backup
)
2) No for master, optional for msdb and model; Oops: you can reorganise just
indexes, not data, considering clustered indexes as indexes and not data...
3)NEVER !!!
4)No for master, optional for msdb and model
5) and 6) As you like.
Generally, the recovery strategy for the system databases differs from the
one adopted for User databases, and a strategy too "regular" could be not so
efficient (suppose you plan a weekly - ora dayly - strategy, but on Tuesday
(for example) some big migration or some big deployment produces a lot of
updates on your system databases: I suggest a backup as soon as possible,
because a crash before the nightly batches could mean an important loss.
Gilberto Zampatti
"Dave" wrote:

> Hi,
> I am new to SQL 2000 Server and as far as I have read, it seems that I
> should backup the Master, Model and MSDB databases.
> However, Should I...
> 1.) Backup the transaction log as part of the maintenance plan?
> 2.) Reorganize data and index pages?
> 3.) Remove unused space from database files?
> 4.) Check database integrity and should I include or exclude indexes? If
> indexes are included/excluded, should I check to Attempt to repair any min
or
> problems and should I perform these checks before doing backups?
> 5.) Create a folder for each database?
> 6.) Remove files older than the default of 4 weeks or should I extend the
> period?
> Lastly,
> 7.) Write history to the table msdb.dbo.sysdbmaintplan_history and should
I
> limit rows to 1k, 5k, 10k, 100k rows for this plan?
> Thank You in advance,
> Dave

Backing up the Master, Model and MSDB databases

Hi,
I am new to SQL 2000 Server and as far as I have read, it seems that I
should backup the Master, Model and MSDB databases.
However, Should I...
1.) Backup the transaction log as part of the maintenance plan?
2.) Reorganize data and index pages?
3.) Remove unused space from database files?
4.) Check database integrity and should I include or exclude indexes? If
indexes are included/excluded, should I check to Attempt to repair any minor
problems and should I perform these checks before doing backups?
5.) Create a folder for each database?
6.) Remove files older than the default of 4 weeks or should I extend the
period?
Lastly,
7.) Write history to the table msdb.dbo.sysdbmaintplan_history and should I
limit rows to 1k, 5k, 10k, 100k rows for this plan?
Thank You in advance,
DaveTry to give an answer to all of your numbered qustions, but remember that:
a) Is a good practice make a backup of your system database whenever you've
done some action that updates them; so, regarding the master, for example,
any CREATE, ALTER or DROP statement will surely update it, and make a backup
is a good idea; regarding the MSDB, each create, alter or drop of some Job,
Alert, Operator or any SSIS implementation, etc. will update it; regarding
the model, if you modify it could be a good idea make a backup.
About your qustions:
1) No for master database (you CANNOT backup transaction log of the master
DB!), optional for MSDB and model (but this means you apply a recovery
strategy, and you should carefully consider the interval between each backup)
2) No for master, optional for msdb and model; Oops: you can reorganise just
indexes, not data, considering clustered indexes as indexes and not data...
3)NEVER !!!
4)No for master, optional for msdb and model
5) and 6) As you like.
Generally, the recovery strategy for the system databases differs from the
one adopted for User databases, and a strategy too "regular" could be not so
efficient (suppose you plan a weekly - ora dayly - strategy, but on Tuesday
(for example) some big migration or some big deployment produces a lot of
updates on your system databases: I suggest a backup as soon as possible,
because a crash before the nightly batches could mean an important loss.
Gilberto Zampatti
"Dave" wrote:
> Hi,
> I am new to SQL 2000 Server and as far as I have read, it seems that I
> should backup the Master, Model and MSDB databases.
> However, Should I...
> 1.) Backup the transaction log as part of the maintenance plan?
> 2.) Reorganize data and index pages?
> 3.) Remove unused space from database files?
> 4.) Check database integrity and should I include or exclude indexes? If
> indexes are included/excluded, should I check to Attempt to repair any minor
> problems and should I perform these checks before doing backups?
> 5.) Create a folder for each database?
> 6.) Remove files older than the default of 4 weeks or should I extend the
> period?
> Lastly,
> 7.) Write history to the table msdb.dbo.sysdbmaintplan_history and should I
> limit rows to 1k, 5k, 10k, 100k rows for this plan?
> Thank You in advance,
> Dave