Restored All Database Except for Master

Hi there,
Yesterday we built a new SQL server 2000 SP3, we restored all company
database using our b-up software. We tested them and our apps seems to work
fine against the newly built SQL server.
Question that is burning my head is: we restored everything except the
MASTER, MODEL, MSDB and PUBS. It was a matter of not knowing if they MUST be
restored together with our own databases.
Mind you, all our apps can talk and write and no problem at all. Do we still
need to restore these ones to our new SQL server?
Any advises or suggestions is much appreciated. Any questions is appreciated
too.
TIA
DMC
You might want to browse thru these to see why you may or may not want to
move the system dbs and what is involved. By the way there is nothing
special about Pubs, it is a sample db and is usually removed from production
servers.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"dmc" <dario@.semiconductor.com> wrote in message
news:ebjbO6z9EHA.2984@.TK2MSFTNGP09.phx.gbl...
> Hi there,
> Yesterday we built a new SQL server 2000 SP3, we restored all company
> database using our b-up software. We tested them and our apps seems to
> work
> fine against the newly built SQL server.
> Question that is burning my head is: we restored everything except the
> MASTER, MODEL, MSDB and PUBS. It was a matter of not knowing if they MUST
> be
> restored together with our own databases.
> Mind you, all our apps can talk and write and no problem at all. Do we
> still
> need to restore these ones to our new SQL server?
> Any advises or suggestions is much appreciated. Any questions is
> appreciated
> too.
> TIA
> DMC
>

Restored All Database Except for Master

Hi there,
Yesterday we built a new SQL server 2000 SP3, we restored all company
database using our b-up software. We tested them and our apps seems to work
fine against the newly built SQL server.
Question that is burning my head is: we restored everything except the
MASTER, MODEL, MSDB and PUBS. It was a matter of not knowing if they MUST be
restored together with our own databases.
Mind you, all our apps can talk and write and no problem at all. Do we still
need to restore these ones to our new SQL server?
Any advises or suggestions is much appreciated. Any questions is appreciated
too.
TIA
DMCYou might want to browse thru these to see why you may or may not want to
move the system dbs and what is involved. By the way there is nothing
special about Pubs, it is a sample db and is usually removed from production
servers.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"dmc" <dario@.semiconductor.com> wrote in message
news:ebjbO6z9EHA.2984@.TK2MSFTNGP09.phx.gbl...
> Hi there,
> Yesterday we built a new SQL server 2000 SP3, we restored all company
> database using our b-up software. We tested them and our apps seems to
> work
> fine against the newly built SQL server.
> Question that is burning my head is: we restored everything except the
> MASTER, MODEL, MSDB and PUBS. It was a matter of not knowing if they MUST
> be
> restored together with our own databases.
> Mind you, all our apps can talk and write and no problem at all. Do we
> still
> need to restore these ones to our new SQL server?
> Any advises or suggestions is much appreciated. Any questions is
> appreciated
> too.
> TIA
> DMC
>sql

Restored All Database Except for Master

Hi there,
Yesterday we built a new SQL server 2000 SP3, we restored all company
database using our b-up software. We tested them and our apps seems to work
fine against the newly built SQL server.
Question that is burning my head is: we restored everything except the
MASTER, MODEL, MSDB and PUBS. It was a matter of not knowing if they MUST be
restored together with our own databases.
Mind you, all our apps can talk and write and no problem at all. Do we still
need to restore these ones to our new SQL server?
Any advises or suggestions is much appreciated. Any questions is appreciated
too.
TIA
DMCYou might want to browse thru these to see why you may or may not want to
move the system dbs and what is involved. By the way there is nothing
special about Pubs, it is a sample db and is usually removed from production
servers.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"dmc" <dario@.semiconductor.com> wrote in message
news:ebjbO6z9EHA.2984@.TK2MSFTNGP09.phx.gbl...
> Hi there,
> Yesterday we built a new SQL server 2000 SP3, we restored all company
> database using our b-up software. We tested them and our apps seems to
> work
> fine against the newly built SQL server.
> Question that is burning my head is: we restored everything except the
> MASTER, MODEL, MSDB and PUBS. It was a matter of not knowing if they MUST
> be
> restored together with our own databases.
> Mind you, all our apps can talk and write and no problem at all. Do we
> still
> need to restore these ones to our new SQL server?
> Any advises or suggestions is much appreciated. Any questions is
> appreciated
> too.
> TIA
> DMC
>

restore to new db restores less data than what is in the source backup file

I am trying to create sql code that restores a backup of a master database to a new database on the same server. It seems to run correctly as no errors are produced. However, the most recent updates to the master database are not present in the new databases. All databases are using the Full recovery model. What is really strange is that if I do (what I think is) the same function in Enterprise Administrator, the restore works fine! For both methods I used the same backup file!



Any and all help is sincerely appreciated.


The master databases from which the backups are made start with MODTRNMaster

The databases which are created from the restores start with M1_ and M2_. (We call them training room databases.)



My script for backing up the master databases:



-- Backup the master training database

backup database MODTRNMaster
to disk = 'f:\bkup\MODTRNMaster.bak'

backup database MODTRNMaster_IMG
to disk = 'f:\bkup\MODTRNMaster_IMG.bak'

backup database MODTRNMaster_MNC
to disk = 'f:\bkup\MODTRNMaster_MNC.bak'

backup database MODTRNMaster_VM
to disk = 'f:\bkup\MODTRNMaster_VM.bak'

go


This is the restore script for restoring the first training room databases. Im hoping that there is just something simple that Im overlooking in these restore statements! J



-- Restore the backup of the master training database into the

-- training room #1 database.

use master
go

drop database M1_MSLH
go

restore database M1_MSLH
from disk = 'f:\bkup\MODTRNMaster.bak'
with move 'DEV5_Data' to 'f:\mssql\data\M1_MLSH.mdf',
move 'MM' to 'f:\mssql\data\M1_MLSH_1.mdf',
move 'AMB' to 'f:\mssql\data\M1_MLSH_2.mdf',
move 'DM' to 'f:\mssql\data\M1_MLSH_3.mdf',
move 'IMM' to 'f:\mssql\data\M1_MLSH_4.mdf',
move 'ED' to 'f:\mssql\data\M1_MLSH_5.mdf',
move 'DEV5_Log' to 'f:\mssql\log\M1_MLSH_log.ldf',
recovery

go



Thanks in advance

:eek:

:eek:that surely sounds like some magic. I do not know off the the top of my head what the problem could be but you should only have one mdf file and the rest of your data files should be ndfs.|||I am trying to create sql code that restores a backup of a master database to a new database on the same server. It seems to run correctly as no errors are produced. However, the most recent updates to the master database are not present in the new databases. All databases are using the Full recovery model. What is really strange is that if I do (what I think is) the same function in Enterprise Administrator, the restore works fine! For both methods I used the same backup file!

Are you sure that the master database is in full recovery mode? I did not think that was possible and/or mattered.

Also, even if it is in full recovery, your restore script indicated that you had restored only the last full backup (.BAK) file and had not restored any transaction logs (.TRN). Without restoring the transaction logs, you will only restore the database to the point in time when the last full backup completed; any transacations performed after that will not get restored.

Finally, I have to ask: why are you restoring the master database? I'm not sure that doing so gets you anything (except maybe practice).

Regards,

hmscott|||sorry. I should have been a little clearer. :o It is not actually THE master database that I'm backing up. We are having some training sessions for users of a new system. The trainer makes his updates in a database named MODTRNMaster (the master database for our purposes). At night I am restoring into 2 individual training databases M1_MLSH and M2_MLSH that the users are accessing.

No transaction log backups are being done. These databases are only being accessed during the day. At night there is no activity in those databases. At night I backup MODTRNMaster and then immediately (attempt to) restore the backup file as M1_MLSH and then again as M2_MLSH.|||You need to add with init to your backup commands, or with file = # to the restore commands. By default, SQL Server will append your backup to the exisiting file (you may have noticed them getting bigger), and restore from the first backup found. Do this and get back to us with the results:

restore headeronly from disk = 'f:\bkup\MODTRNMaster.bak'|||Thanks So much for your suggestion! Adding the "init" parameter to the backup database statement was exactly what was needed!! :D

Restore system dbs from SP3 to SP3a?

Can system databases (master, model, msdb) backed up from SQL2k SP3 be restored to an instance of SP3a? Can they be restored from SP3a to SP3? TIA!Not going to happen buddy. try installing a fresh copy of sql server somewhere else upgrade to sp3, restore your system db's there, upgrade to sp3a then move the system db's to the live server. hope this helps.|||Thanks - that's what I thought. However, how can it be determined which SP (3 or 3a) a given instance is running? @.@.version returns 8.00.760 for both of them, & Properties in EM show SP3 for both. I remember there being a way to find the build number, but I don't know how to get it. TIA.|||Check with MS website at the SP3/SP3a download pages. They usually have a section that tells you how to determine which SP you're currently running under.|||Even better: http://www.sqlteam.com/item.asp?ItemID=8318

restore system databases to server with different/alternate data p

I finally figured out how to do this when the source server has its master,
model, msdb, and tempdb databases in a different location than the target
server.
You may have to interpret some of the file names and locations here:
If you are going to restore system databases from a source who’s data
directory path is different from this computer, use the following procedure:
1.WARNING you must be able to detach and reattach the model and msdb
databases, therefore, you should:
oOpen enterprise manager
oRestore the model database from the source server
oRestore the msdb database from the source server
2.Stop the MSSQL service.
3.Go to Start menu and open a command prompt.
4.Change to directory C:\Program files\ Microsoft SQL Server\MSSQL\binn
5.Start sql server with: sqlservr –m –c -f (this brings the system up in
Single User Mode; if you add -T3608 (don’t use a lowercase t) so SQL Server
does not recover any database except the master database, the restore
database master command will complain about not having a tempdb).
6.Go to Start menu and open a second command prompt.
7.Change to directory where the backup files are (e.g. E:\ MSSQL\BACKUP).
8.Type (case sensitive): osql –S serverName -E
oThis logs in to the specified server and logs in with the Windows user
currently logged in.
oYou should see a command prompt that looks like: >1
9.Type:
restore database master
from disk='e:\mssql\backup\from_prod\master_bk.bak'
with move 'master' to 'e:\mssql\data\master.mdf', move 'mastlog' to
'e:\mssql\data\mastlog.ldf'
(the ‘with move’ part is necessary because the location of the files is
changing)
go
oWhen that completes, both the osql session and the sqlservr session will
be shut down. You should see:
The master database has been successfully restored. Shutting down SQL Server
SQL Server is terminating this process.
10.to move the model database, start sql server with sqlservr -m -c -f -T3608
11.in the other window, run osql –S serverName –E again and type
use master
go
sp_detach_db 'model'
go
sp_attach_single_file_db 'model','e:\mssql\data\model.mdf'
go
sp_detach_db 'msdb'
go
exit
12.Stop the server with Ctrl+C
13.Restart the server with sqlservr -m -c –f
14.in the other window, run osql –S serverName –E again and type
use master
go
sp_attach_single_file_db 'msdb','e:\mssql\data\msdbdata.mdf'
go
Alter database tempdb modify file (name = tempdev, filename =
'E:\MSSQL\Datatempdb.mdf')
go
{you will see: File 'tempdev' modified in sysaltfiles. Delete old file after
restarting SQLServer.}
Alter database tempdb modify file (name = templog, filename =
'E:\MSSQL\Datatemplog.ldf')
go
{you will see: File 'templog' modified in sysaltfiles. Delete old file after
restarting SQL Server.}
exit
oyou will not actually have to delete any files because they are already in
the correct place. The master database just had to be modified so that it
would know that.
15.Stop the server with Ctrl+C
oYou should now be able to restart the sql cluster resources (or the sql
server service if not using a cluster)
16.start the normal sql service and test by opening Enterprise Manager and
connecting to the server. If it hangs up, you might just have to restart the
service again.
oNote: On a fresh restore the user databases will be listed as Suspect.
You must now restore each of the user databases to the correct file location.
This can easily be done with Enterprise Manager (assuming it doesn’t hang up
or take forever for the restore database dialog box to come up, which usually
is the case, actually).
I forgot to mention that if the server name is different, you are going to
have problems with your scheduled jobs. Run this script to fix:
'replace the newName with the name of the new server and the oldName with
the name of the old server.
use msdb
update sysjobs
set sysjobs.originating_server = 'newName'
where sysjobs.originating_server = 'oldName'
select * from msdb..sysjobs order by name --to verify
Oh, and by the way, your backup "devices" will still be set to the same
location and thus will need to be recreated.

restore system databases to server with different/alternate data p

I finally figured out how to do this when the source server has its master,
model, msdb, and tempdb databases in a different location than the target
server.
You may have to interpret some of the file names and locations here:
If you are going to restore system databases from a source who’s data
directory path is different from this computer, use the following procedure:
1. WARNING you must be able to detach and reattach the model and msdb
databases, therefore, you should:
o Open enterprise manager
o Restore the model database from the source server
o Restore the msdb database from the source server
2. Stop the MSSQL service.
3. Go to Start menu and open a command prompt.
4. Change to directory C:\Program files\ Microsoft SQL Server\MSSQL\binn
5. Start sql server with: sqlservr –m –c -f (this brings the system up i
n
Single User Mode; if you add -T3608 (don’t use a lowercase t) so SQL Serve
r
does not recover any database except the master database, the restore
database master command will complain about not having a tempdb).
6. Go to Start menu and open a second command prompt.
7. Change to directory where the backup files are (e.g. E:\ MSSQL\BACKUP).
8. Type (case sensitive): osql –S serverName -E
o This logs in to the specified server and logs in with the Windows user
currently logged in.
o You should see a command prompt that looks like: >1
9. Type:
restore database master
from disk='e:\mssql\backup\from_prod\master_b
k.bak'
with move 'master' to 'e:\mssql\data\master.mdf', move 'mastlog' to
'e:\mssql\data\mastlog.ldf'
(the ‘with move’ part is necessary because the location of the files is
changing)
go
o When that completes, both the osql session and the sqlservr session will
be shut down. You should see:
The master database has been successfully restored. Shutting down SQL Server
SQL Server is terminating this process.
10. to move the model database, start sql server with sqlservr -m -c -f -T36
08
11. in the other window, run osql –S serverName –E again and type
use master
go
sp_detach_db 'model'
go
sp_attach_single_file_db 'model','e:\mssql\data\model.mdf'
go
sp_detach_db 'msdb'
go
exit
12. Stop the server with Ctrl+C
13. Restart the server with sqlservr -m -c –f
14. in the other window, run osql –S serverName –E again and type
use master
go
sp_attach_single_file_db 'msdb','e:\mssql\data\msdbdata.mdf'
go
Alter database tempdb modify file (name = tempdev, filename =
'E:\MSSQL\Datatempdb.mdf')
go
{you will see: File 'tempdev' modified in sysaltfiles. Delete old file
after
restarting SQLServer.}
Alter database tempdb modify file (name = templog, filename =
'E:\MSSQL\Datatemplog.ldf')
go
{you will see: File 'templog' modified in sysaltfiles. Delete old file
after
restarting SQL Server.}
exit
o you will not actually have to delete any files because they are already in
the correct place. The master database just had to be modified so that it
would know that.
15. Stop the server with Ctrl+C
o You should now be able to restart the sql cluster resources (or the sql
server service if not using a cluster)
16. start the normal sql service and test by opening Enterprise Manager and
connecting to the server. If it hangs up, you might just have to restart the
service again.
o Note: On a fresh restore the user databases will be listed as Suspect.
You must now restore each of the user databases to the correct file location
.
This can easily be done with Enterprise Manager (assuming it doesn’t hang
up
or take forever for the restore database dialog box to come up, which usuall
y
is the case, actually).I forgot to mention that if the server name is different, you are going to
have problems with your scheduled jobs. Run this script to fix:
'replace the newName with the name of the new server and the oldName with
the name of the old server.
use msdb
update sysjobs
set sysjobs.originating_server = 'newName'
where sysjobs.originating_server = 'oldName'
select * from msdb..sysjobs order by name --to verify
Oh, and by the way, your backup "devices" will still be set to the same
location and thus will need to be recreated.

restore system databases to server with different/alternate data p

I finally figured out how to do this when the source server has its master,
model, msdb, and tempdb databases in a different location than the target
server.
You may have to interpret some of the file names and locations here:
If you are going to restore system databases from a source whoâ's data
directory path is different from this computer, use the following procedure:
1. WARNING you must be able to detach and reattach the model and msdb
databases, therefore, you should:
o Open enterprise manager
o Restore the model database from the source server
o Restore the msdb database from the source server
2. Stop the MSSQL service.
3. Go to Start menu and open a command prompt.
4. Change to directory C:\Program files\ Microsoft SQL Server\MSSQL\binn
5. Start sql server with: sqlservr â'm â'c -f (this brings the system up in
Single User Mode; if you add -T3608 (donâ't use a lowercase t) so SQL Server
does not recover any database except the master database, the restore
database master command will complain about not having a tempdb).
6. Go to Start menu and open a second command prompt.
7. Change to directory where the backup files are (e.g. E:\ MSSQL\BACKUP).
8. Type (case sensitive): osql â'S serverName -E
o This logs in to the specified server and logs in with the Windows user
currently logged in.
o You should see a command prompt that looks like: >1
9. Type:
restore database master
from disk='e:\mssql\backup\from_prod\master_bk.bak'
with move 'master' to 'e:\mssql\data\master.mdf', move 'mastlog' to
'e:\mssql\data\mastlog.ldf'
(the â'with moveâ' part is necessary because the location of the files is
changing)
go
o When that completes, both the osql session and the sqlservr session will
be shut down. You should see:
The master database has been successfully restored. Shutting down SQL Server
SQL Server is terminating this process.
10. to move the model database, start sql server with sqlservr -m -c -f -T3608
11. in the other window, run osql â'S serverName â'E again and type
use master
go
sp_detach_db 'model'
go
sp_attach_single_file_db 'model','e:\mssql\data\model.mdf'
go
sp_detach_db 'msdb'
go
exit
12. Stop the server with Ctrl+C
13. Restart the server with sqlservr -m -c â'f
14. in the other window, run osql â'S serverName â'E again and type
use master
go
sp_attach_single_file_db 'msdb','e:\mssql\data\msdbdata.mdf'
go
Alter database tempdb modify file (name = tempdev, filename = 'E:\MSSQL\Datatempdb.mdf')
go
{you will see: File 'tempdev' modified in sysaltfiles. Delete old file after
restarting SQLServer.}
Alter database tempdb modify file (name = templog, filename = 'E:\MSSQL\Datatemplog.ldf')
go
{you will see: File 'templog' modified in sysaltfiles. Delete old file after
restarting SQL Server.}
exit
o you will not actually have to delete any files because they are already in
the correct place. The master database just had to be modified so that it
would know that.
15. Stop the server with Ctrl+C
o You should now be able to restart the sql cluster resources (or the sql
server service if not using a cluster)
16. start the normal sql service and test by opening Enterprise Manager and
connecting to the server. If it hangs up, you might just have to restart the
service again.
o Note: On a fresh restore the user databases will be listed as Suspect.
You must now restore each of the user databases to the correct file location.
This can easily be done with Enterprise Manager (assuming it doesnâ't hang up
or take forever for the restore database dialog box to come up, which usually
is the case, actually).I forgot to mention that if the server name is different, you are going to
have problems with your scheduled jobs. Run this script to fix:
'replace the newName with the name of the new server and the oldName with
the name of the old server.
use msdb
update sysjobs
set sysjobs.originating_server = 'newName'
where sysjobs.originating_server = 'oldName'
select * from msdb..sysjobs order by name --to verify
Oh, and by the way, your backup "devices" will still be set to the same
location and thus will need to be recreated.

Restore SQL server, Login failure

I restored a DB to another server and then i used the stored procedures

exec sp_addlogin on the master DB and the exec sp_change_users_login on the DB that I have restored. When i try to run a sproc I am getting

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

I have used windows authentication to login to connect to the server using sql management studio

Am i missing something. Thankyou for the help

How do you call the stored procedure and what does the stored procedure do?

Thanks
Laurentiu

Restore SQL master database from a file

Hello,

I need to restore the Master DB in my SQL 2k server (with sp3). The
problem is that i don't have SQL backups of this file I only have
general backup of the entire c:\ drive i made using NTBackup. So i
tried all I know and succesfully run the rebuildm utility. Now when I
try to restore it from the general backup (not SQL backup) using
"restore database master from gen_backup" i got error: "The file on
device 'gen_backup' is not a valid Microsoft Tape Format backup set."
RESTORE DATABASE is terminating abnormally.
Any ideas how I can restore it?<Moti.Ba@.gmail.com> wrote in message
news:1105264654.916229.258480@.c13g2000cwb.googlegr oups.com...
> Hello,
> I need to restore the Master DB in my SQL 2k server (with sp3). The
> problem is that i don't have SQL backups of this file I only have
> general backup of the entire c:\ drive i made using NTBackup. So i
> tried all I know and succesfully run the rebuildm utility. Now when I
> try to restore it from the general backup (not SQL backup) using
> "restore database master from gen_backup" i got error: "The file on
> device 'gen_backup' is not a valid Microsoft Tape Format backup set."
> RESTORE DATABASE is terminating abnormally.
> Any ideas how I can restore it?

Is this the same problem you had a few months ago?

http://groups.google.co.uk/groups?h...news.bluewin.ch

If you have the master.mdf and mastlog.ldf files (if you can restore them
from your NTBackup backup set), then you can try the process I described
earlier, although I haven't tried it myself, so I can't say for sure that it
will work.

Whatever happens, you need to set up proper MSSQL backups to make sure you
don't have this problem again - you can use the maintenance plan wizard to
get started quickly. You should also check out the Books Online section on
"Backing Up and Restoring Databases".

Simon|||(Moti.Ba@.gmail.com) writes:
> I need to restore the Master DB in my SQL 2k server (with sp3). The
> problem is that i don't have SQL backups of this file I only have
> general backup of the entire c:\ drive i made using NTBackup. So i
> tried all I know and succesfully run the rebuildm utility. Now when I
> try to restore it from the general backup (not SQL backup) using
> "restore database master from gen_backup" i got error: "The file on
> device 'gen_backup' is not a valid Microsoft Tape Format backup set."
> RESTORE DATABASE is terminating abnormally.
> Any ideas how I can restore it?

You cannot use the RESTORE command in SQL Server to read something
from a NT Backup, as far as I know. You first need to restore the
master.mdf and master.ldf from backup with NT Backup.

However, it is far from certain that the files are usuable, because if
you backup database files with NT backup, there is no guarantee that they
are transactionally consistent. You can get all sorts of rubbish. That is,
if SQL Server was running when you ran NT backup. If SQL Server wasn't
running the backups should be OK.

There are somewhat better odds with master than other database, because
there is little update traffic in that database, and the database is small.

But nevertheless, before you actually try to use it as a master database,
just try to attach it as a regular user database first and run DBCC CHECKDB
on it.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Restore puts copy of user tables in master

Environment is SQL Server 2000 64 bit.
I restore from a script 'my' database, this works fine. However, all
the tables are also found in master, no data though.
Anyone experienced this?"Emille378" <dishonty@.seidata.com> wrote in message
news:d25b2692.0405050650.854b85c@.posting.google.co m...
> Environment is SQL Server 2000 64 bit.
> I restore from a script 'my' database, this works fine. However, all
> the tables are also found in master, no data though.
> Anyone experienced this?

Can you show us the script?

Restore puts copy of user tables in master

Environment is SQL Server 2000 64 bit.
I restore from a script 'my' database, this works fine. However, all
the tables are also found in master, no data though.
Anyone experienced this?"Emille378" <dishonty@.seidata.com> wrote in message
news:d25b2692.0405050650.854b85c@.posting.google.co m...
> Environment is SQL Server 2000 64 bit.
> I restore from a script 'my' database, this works fine. However, all
> the tables are also found in master, no data though.
> Anyone experienced this?

Can you show us the script?|||"Greg D. Moore \(Strider\)" <mooregr_deleteth1s@.greenms.com> wrote in message news:<%fgmc.160405$M3.149305@.twister.nyroc.rr.com>...
> "Emille378" <dishonty@.seidata.com> wrote in message
> news:d25b2692.0405050650.854b85c@.posting.google.co m...
> > Environment is SQL Server 2000 64 bit.
> > I restore from a script 'my' database, this works fine. However, all
> > the tables are also found in master, no data though.
> > Anyone experienced this?
> Can you show us the script?

RESTORE DATABASE XX
FROM DISK = 'g:\XX_db.BAK'
WITH STATS = 10, REPLACE,
MOVE 'XX_data' TO 'h:\Program Files\Microsoft SQL
Server\MSSQL\Data\XX_Data.mdf',
MOVE 'XX_log' TO 'g:\logs\XX_Log.ldf',
MOVE 'XX_Indx' TO 'h:\Program Files\Microsoft SQL
Server\MSSQL\Data\XX_Indx_Data.NDF'

Restore of System databases... in earlier to SQL 2K versions....

Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
How did earlier versions of SQL Server 2K use to restore the system
databases?
http://support.microsoft.com/default...b;en-us;169039
As per the above link it seems to be there is no trace of restoring the
MASTER or MSDB databases as explained in SQL 2K documentation.
Thank you for your comment,
Allen
Restore of the system databases has worked the same way across all versions of SQL Server (well,
msdb was introduced in 6.0).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"AllenHubatka" <AllenHubtka_67@.hotmail.com> wrote in message
news:uhvZCEFqFHA.3160@.TK2MSFTNGP14.phx.gbl...
>
> Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
> How did earlier versions of SQL Server 2K use to restore the system
> databases?
> http://support.microsoft.com/default...b;en-us;169039
> As per the above link it seems to be there is no trace of restoring the
> MASTER or MSDB databases as explained in SQL 2K documentation.
> Thank you for your comment,
> Allen
>
>
>

Restore of System databases... in earlier to SQL 2K versions....

Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
How did earlier versions of SQL Server 2K use to restore the system
databases?
http://support.microsoft.com/default.aspx?scid=kb;en-us;169039
As per the above link it seems to be there is no trace of restoring the
MASTER or MSDB databases as explained in SQL 2K documentation.
Thank you for your comment,
AllenRestore of the system databases has worked the same way across all versions of SQL Server (well,
msdb was introduced in 6.0).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"AllenHubatka" <AllenHubtka_67@.hotmail.com> wrote in message
news:uhvZCEFqFHA.3160@.TK2MSFTNGP14.phx.gbl...
>
> Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
> How did earlier versions of SQL Server 2K use to restore the system
> databases?
> http://support.microsoft.com/default.aspx?scid=kb;en-us;169039
> As per the above link it seems to be there is no trace of restoring the
> MASTER or MSDB databases as explained in SQL 2K documentation.
> Thank you for your comment,
> Allen
>
>
>

Restore of System databases... in earlier to SQL 2K versions....

Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
How did earlier versions of SQL Server 2K use to restore the system
databases?
http://support.microsoft.com/defaul...kb;en-us;169039
As per the above link it seems to be there is no trace of restoring the
MASTER or MSDB databases as explained in SQL 2K documentation.
Thank you for your comment,
AllenRestore of the system databases has worked the same way across all versions
of SQL Server (well,
msdb was introduced in 6.0).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"AllenHubatka" <AllenHubtka_67@.hotmail.com> wrote in message
news:uhvZCEFqFHA.3160@.TK2MSFTNGP14.phx.gbl...
>
> Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2
K?
> How did earlier versions of SQL Server 2K use to restore the system
> databases?
> http://support.microsoft.com/defaul...kb;en-us;169039
> As per the above link it seems to be there is no trace of restoring the
> MASTER or MSDB databases as explained in SQL 2K documentation.
> Thank you for your comment,
> Allen
>
>
>

Restore of master

Tomorrow we are updating a server from 7.0 to 2000 w/
these steps:
1. I am copying the user databases off onto another
server.
2. We'll uninstall 7.0.
3. We'll install Sql Server 2000.
4. We'll copy the user databases back and let the upgrade
happen "on the fly".
My question: how do I restore the master and/or msdb
database? Of course I can make a backup but it will be a
7.0 backup. Is it as simple as doing a restore of the
master from the masterxxx.bak file that is 7.0?You cannot restore system databases across version, most time not even
across service packs. To automate the info in the system databases, you need
to let the install program update the 7.0 install to 2000.
So, you have to consider each piece of information in the system databases
and what you want to bring over and what you can do automatically. One way
is to study the system tables and from there create a list of what is stored
in the system databases and how to bring that over (and whether you can
"re-type" of want to automate). The main things are usually (I probably
forget some stuff, been away for a month):
Master:
Logins
Linked servers
Backupdevices
Msdb:
Jobs
Alerts
And don't forget model, if you've done any changes to it.
Post back if you want to know more about a certain topic.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"SSB" <anonymous@.discussions.microsoft.com> wrote in message
news:292501c3e113$52350320$a501280a@.phx.gbl...

quote:

---

> Tomorrow we are updating a server from 7.0 to 2000 w/
> these steps:
> 1. I am copying the user databases off onto another
> server.
> 2. We'll uninstall 7.0.
> 3. We'll install Sql Server 2000.
> 4. We'll copy the user databases back and let the upgrade
> happen "on the fly".
> My question: how do I restore the master and/or msdb
> database? Of course I can make a backup but it will be a
> 7.0 backup. Is it as simple as doing a restore of the
> master from the masterxxx.bak file that is 7.0?

---

|||What you outlined below was exactly what I was planning
on, because I have a certain amount of concern over
letting sql server do the upgrade. I've seen small
problems with upgrades on the client tools and so I've
never felt comfortable with an upgrade of sql server
itself.
Do you agree with my assessment? Isn't it always better
to do a fresh install if at all possible?

quote:

---

>--Original Message--
>You cannot restore system databases across version, most

---

time not even

quote:

---

>across service packs. To automate the info in the system

---

databases, you need

quote:

---

>to let the install program update the 7.0 install to 2000.
>So, you have to consider each piece of information in the

---

system databases

quote:

---

>and what you want to bring over and what you can do

---

automatically. One way

quote:

---

>is to study the system tables and from there create a

---

list of what is stored

quote:

---

>in the system databases and how to bring that over (and

---

whether you can

quote:

---

>"re-type" of want to automate). The main things are

---

usually (I probably

quote:

---

>forget some stuff, been away for a month):
>Master:
>Logins
>Linked servers
>Backupdevices
>Msdb:
>Jobs
>Alerts
>And don't forget model, if you've done any changes to it.
>Post back if you want to know more about a certain topic.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?

---

oi=djq&as_ugroup=microsoft.public.sqlserver

quote:

---

>
>"SSB" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:292501c3e113$52350320$a501280a@.phx.gbl...
upgrade[QUOTE]
a[QUOTE]
>
>.
>

---

|||Yes, I generally prefer fresh installations over upgrades. However, if you
have a more complex installation (again, regarding the stuff in your system
databases), then the effort to bring that over is an issue to weigh in, of
course. Also, another factor is how familiar you are with what is in the
system databases and how to copy or re-cerate that info.
In many cases, I prefer fresh install over upgrades for SQL Server as well.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"SSB" <anonymous@.discussions.microsoft.com> wrote in message
news:2a8b01c3e12b$6bf07570$a401280a@.phx.gbl...[QUOTE]
> What you outlined below was exactly what I was planning
> on, because I have a certain amount of concern over
> letting sql server do the upgrade. I've seen small
> problems with upgrades on the client tools and so I've
> never felt comfortable with an upgrade of sql server
> itself.
> Do you agree with my assessment? Isn't it always better
> to do a fresh install if at all possible?
>
> time not even
> databases, you need
> system databases
> automatically. One way
> list of what is stored
> whether you can
> usually (I probably
> oi=djq&as_ugroup=microsoft.public.sqlserver
> message
> upgrade
> a

Restore of master

Tomorrow we are updating a server from 7.0 to 2000 w/
these steps:
1. I am copying the user databases off onto another
server.
2. We'll uninstall 7.0.
3. We'll install Sql Server 2000.
4. We'll copy the user databases back and let the upgrade
happen "on the fly".
My question: how do I restore the master and/or msdb
database? Of course I can make a backup but it will be a
7.0 backup. Is it as simple as doing a restore of the
master from the masterxxx.bak file that is 7.0?You cannot restore system databases across version, most time not even
across service packs. To automate the info in the system databases, you need
to let the install program update the 7.0 install to 2000.
So, you have to consider each piece of information in the system databases
and what you want to bring over and what you can do automatically. One way
is to study the system tables and from there create a list of what is stored
in the system databases and how to bring that over (and whether you can
"re-type" of want to automate). The main things are usually (I probably
forget some stuff, been away for a month):
Master:
Logins
Linked servers
Backupdevices
Msdb:
Jobs
Alerts
And don't forget model, if you've done any changes to it.
Post back if you want to know more about a certain topic.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"SSB" <anonymous@.discussions.microsoft.com> wrote in message
news:292501c3e113$52350320$a501280a@.phx.gbl...
> Tomorrow we are updating a server from 7.0 to 2000 w/
> these steps:
> 1. I am copying the user databases off onto another
> server.
> 2. We'll uninstall 7.0.
> 3. We'll install Sql Server 2000.
> 4. We'll copy the user databases back and let the upgrade
> happen "on the fly".
> My question: how do I restore the master and/or msdb
> database? Of course I can make a backup but it will be a
> 7.0 backup. Is it as simple as doing a restore of the
> master from the masterxxx.bak file that is 7.0?|||What you outlined below was exactly what I was planning
on, because I have a certain amount of concern over
letting sql server do the upgrade. I've seen small
problems with upgrades on the client tools and so I've
never felt comfortable with an upgrade of sql server
itself.
Do you agree with my assessment? Isn't it always better
to do a fresh install if at all possible?
>--Original Message--
>You cannot restore system databases across version, most
time not even
>across service packs. To automate the info in the system
databases, you need
>to let the install program update the 7.0 install to 2000.
>So, you have to consider each piece of information in the
system databases
>and what you want to bring over and what you can do
automatically. One way
>is to study the system tables and from there create a
list of what is stored
>in the system databases and how to bring that over (and
whether you can
>"re-type" of want to automate). The main things are
usually (I probably
>forget some stuff, been away for a month):
>Master:
>Logins
>Linked servers
>Backupdevices
>Msdb:
>Jobs
>Alerts
>And don't forget model, if you've done any changes to it.
>Post back if you want to know more about a certain topic.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"SSB" <anonymous@.discussions.microsoft.com> wrote in
message
>news:292501c3e113$52350320$a501280a@.phx.gbl...
>> Tomorrow we are updating a server from 7.0 to 2000 w/
>> these steps:
>> 1. I am copying the user databases off onto another
>> server.
>> 2. We'll uninstall 7.0.
>> 3. We'll install Sql Server 2000.
>> 4. We'll copy the user databases back and let the
upgrade
>> happen "on the fly".
>> My question: how do I restore the master and/or msdb
>> database? Of course I can make a backup but it will be
a
>> 7.0 backup. Is it as simple as doing a restore of the
>> master from the masterxxx.bak file that is 7.0?
>
>.
>|||Yes, I generally prefer fresh installations over upgrades. However, if you
have a more complex installation (again, regarding the stuff in your system
databases), then the effort to bring that over is an issue to weigh in, of
course. Also, another factor is how familiar you are with what is in the
system databases and how to copy or re-cerate that info.
In many cases, I prefer fresh install over upgrades for SQL Server as well.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"SSB" <anonymous@.discussions.microsoft.com> wrote in message
news:2a8b01c3e12b$6bf07570$a401280a@.phx.gbl...
> What you outlined below was exactly what I was planning
> on, because I have a certain amount of concern over
> letting sql server do the upgrade. I've seen small
> problems with upgrades on the client tools and so I've
> never felt comfortable with an upgrade of sql server
> itself.
> Do you agree with my assessment? Isn't it always better
> to do a fresh install if at all possible?
> >--Original Message--
> >You cannot restore system databases across version, most
> time not even
> >across service packs. To automate the info in the system
> databases, you need
> >to let the install program update the 7.0 install to 2000.
> >
> >So, you have to consider each piece of information in the
> system databases
> >and what you want to bring over and what you can do
> automatically. One way
> >is to study the system tables and from there create a
> list of what is stored
> >in the system databases and how to bring that over (and
> whether you can
> >"re-type" of want to automate). The main things are
> usually (I probably
> >forget some stuff, been away for a month):
> >
> >Master:
> >Logins
> >Linked servers
> >Backupdevices
> >
> >Msdb:
> >Jobs
> >Alerts
> >
> >And don't forget model, if you've done any changes to it.
> >
> >Post back if you want to know more about a certain topic.
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"SSB" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:292501c3e113$52350320$a501280a@.phx.gbl...
> >> Tomorrow we are updating a server from 7.0 to 2000 w/
> >> these steps:
> >> 1. I am copying the user databases off onto another
> >> server.
> >> 2. We'll uninstall 7.0.
> >> 3. We'll install Sql Server 2000.
> >> 4. We'll copy the user databases back and let the
> upgrade
> >> happen "on the fly".
> >>
> >> My question: how do I restore the master and/or msdb
> >> database? Of course I can make a backup but it will be
> a
> >> 7.0 backup. Is it as simple as doing a restore of the
> >> master from the masterxxx.bak file that is 7.0?
> >
> >
> >.
> >

Restore msdb and master db from files.

Hi all,
My SQL Server crashed and I don't have any backup. So, I install new server, I attach user databases, everythink ok, but i need restore master and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf. Is there any way to do it?
Thanks a lot
Systemspecialist,
Build your SQL Server directory structure *exactly* the same as it was
set up on the old server, and place the .mdf and .ldf files in the same
locations, then start SQL Server. It should just start up. Make sure you
have the same service pack applied on the new box as you did on the old,
before copying the data files over.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Systemspecialist wrote:

> Hi all,
> My SQL Server crashed and I don't have any backup. So, I install new server, I attach user databases, everythink ok, but i need restore master and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf. Is there any way to do it?
> Thanks a lot
|||Hi,
I was about to say the same, but Systemspecialist has already installed,
applied service pack and attached the user databases.
The steps you supposed to do is:-
1. Copy all the MDF and LDF (Including system databases) to a safe directory
2. Install SQl server in same directory as old and apply the same service
pack as old
3. Stop SQL server and SQL Agent
4. Copy all the MDF and LDF files to the same folder
5. STart sql server.
This will start the sql server with the same setup as old.
Thanks
Hari
MCDBA
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:up6u5nJREHA.3300@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Systemspecialist,
> Build your SQL Server directory structure *exactly* the same as it was
> set up on the old server, and place the .mdf and .ldf files in the same
> locations, then start SQL Server. It should just start up. Make sure you
> have the same service pack applied on the new box as you did on the old,
> before copying the data files over.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Systemspecialist wrote:
server, I attach user databases, everythink ok, but i need restore master
and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf.
Is there any way to do it?
>
|||Thanks Hari, you're saying the same thing as me, just better.
Hari wrote:
> Hi,
> I was about to say the same, but Systemspecialist has already installed,
> applied service pack and attached the user databases.
> The steps you supposed to do is:-
> 1. Copy all the MDF and LDF (Including system databases) to a safe directory
> 2. Install SQl server in same directory as old and apply the same service
> pack as old
> 3. Stop SQL server and SQL Agent
> 4. Copy all the MDF and LDF files to the same folder
> 5. STart sql server.
> This will start the sql server with the same setup as old.
> Thanks
> Hari
> MCDBA
>

Restore msdb and master db from files.

Hi all
My SQL Server crashed and I don't have any backup. So, I install new server, I attach user databases, everythink ok, but i need restore master and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf. Is there any way to do it
Thanks a lotSystemspecialist,
Build your SQL Server directory structure *exactly* the same as it was
set up on the old server, and place the .mdf and .ldf files in the same
locations, then start SQL Server. It should just start up. Make sure you
have the same service pack applied on the new box as you did on the old,
before copying the data files over.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Systemspecialist wrote:
> Hi all,
> My SQL Server crashed and I don't have any backup. So, I install new server, I attach user databases, everythink ok, but i need restore master and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf. Is there any way to do it?
> Thanks a lot|||Hi,
I was about to say the same, but Systemspecialist has already installed,
applied service pack and attached the user databases.
The steps you supposed to do is:-
1. Copy all the MDF and LDF (Including system databases) to a safe directory
2. Install SQl server in same directory as old and apply the same service
pack as old
3. Stop SQL server and SQL Agent
4. Copy all the MDF and LDF files to the same folder
5. STart sql server.
This will start the sql server with the same setup as old.
Thanks
Hari
MCDBA
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:up6u5nJREHA.3300@.TK2MSFTNGP09.phx.gbl...
> Systemspecialist,
> Build your SQL Server directory structure *exactly* the same as it was
> set up on the old server, and place the .mdf and .ldf files in the same
> locations, then start SQL Server. It should just start up. Make sure you
> have the same service pack applied on the new box as you did on the old,
> before copying the data files over.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Systemspecialist wrote:
> > Hi all,
> > My SQL Server crashed and I don't have any backup. So, I install new
server, I attach user databases, everythink ok, but i need restore master
and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf.
Is there any way to do it?
> >
> > Thanks a lot
>|||Thanks Hari, you're saying the same thing as me, just better.
Hari wrote:
> Hi,
> I was about to say the same, but Systemspecialist has already installed,
> applied service pack and attached the user databases.
> The steps you supposed to do is:-
> 1. Copy all the MDF and LDF (Including system databases) to a safe directory
> 2. Install SQl server in same directory as old and apply the same service
> pack as old
> 3. Stop SQL server and SQL Agent
> 4. Copy all the MDF and LDF files to the same folder
> 5. STart sql server.
> This will start the sql server with the same setup as old.
> Thanks
> Hari
> MCDBA
>

Restore msdb and master db from files.

Hi all,
My SQL Server crashed and I don't have any backup. So, I install new server,
I attach user databases, everythink ok, but i need restore master and msdb
databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf. Is there a
ny way to do it?
Thanks a lotSystemspecialist,
Build your SQL Server directory structure *exactly* the same as it was
set up on the old server, and place the .mdf and .ldf files in the same
locations, then start SQL Server. It should just start up. Make sure you
have the same service pack applied on the new box as you did on the old,
before copying the data files over.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Systemspecialist wrote:

> Hi all,
> My SQL Server crashed and I don't have any backup. So, I install new serve
r, I attach user databases, everythink ok, but i need restore master and msd
b databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf. Is there
any way to do it?
> Thanks a lot|||Hi,
I was about to say the same, but Systemspecialist has already installed,
applied service pack and attached the user databases.
The steps you supposed to do is:-
1. Copy all the MDF and LDF (Including system databases) to a safe directory
2. Install SQl server in same directory as old and apply the same service
pack as old
3. Stop SQL server and SQL Agent
4. Copy all the MDF and LDF files to the same folder
5. STart sql server.
This will start the sql server with the same setup as old.
Thanks
Hari
MCDBA
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:up6u5nJREHA.3300@.TK2MSFTNGP09.phx.gbl...
> Systemspecialist,
> Build your SQL Server directory structure *exactly* the same as it was
> set up on the old server, and place the .mdf and .ldf files in the same
> locations, then start SQL Server. It should just start up. Make sure you
> have the same service pack applied on the new box as you did on the old,
> before copying the data files over.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Systemspecialist wrote:
>
server, I attach user databases, everythink ok, but i need restore master
and msdb databases from master.mdf , master.ldf and msdb.mdf and msdb.ldf.
Is there any way to do it?[vbcol=seagreen]
>|||Thanks Hari, you're saying the same thing as me, just better.
Hari wrote:
> Hi,
> I was about to say the same, but Systemspecialist has already installed,
> applied service pack and attached the user databases.
> The steps you supposed to do is:-
> 1. Copy all the MDF and LDF (Including system databases) to a safe directo
ry
> 2. Install SQl server in same directory as old and apply the same service
> pack as old
> 3. Stop SQL server and SQL Agent
> 4. Copy all the MDF and LDF files to the same folder
> 5. STart sql server.
> This will start the sql server with the same setup as old.
> Thanks
> Hari
> MCDBA
>