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

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Remedy and Magic databases

Author  Topic 

revolution9
Starting Member

2 Posts

Posted - 2004-09-27 : 11:30:53
Hi all, I am happy I found this forum.

I am a consultant working with Remedy, and we install a product called Magic Total Service Desk.

When it comes to restoring databases we have always been told we need the Master database.

I am currently at a client site to do an upgrade for them, from SQL 7 to SQL 2000, and the procedures I have followed in the past have been to put the databases (Magic and Master) onto the new machine in 7.0 and then upgrade to SQL 2000. I usually restore the master to the new servers but sometimes I have run into issues where I couldn't get into the SQL server again, especially if the drive mappings are different.

I have been doing a lot of reading and learning about database and user migration over the past week, and it seems that there is a consensus that the biggest thing master handles is the database logins. I have a couple of questions:

Are there other things in the master that it could possibly be using for the Magic databases?

Does anyone recommend the copy database wizard?

If I do the upgrade from SQL 7 to SQL 2000 are there any issues after the upgrade that I should address?

Thanks for your help
R9

MuadDBA

628 Posts

Posted - 2004-09-27 : 14:29:09
You need to talk to whoever told you to restore the master database. I can't think of any reason you would want to do this, really...

logins can be scripted
custom stored procedures/extended procedures can be scripted

I can't think of anything int he master database that can't be recreated with a script of some sort, with the exception of the user passwords, and even that can be scripted, just not automatically.

On the other hand, you've obviously seen many things that can be broken by restoring the MASTER database, and you really shouldn't restore the MASTER database to a server from which it wasn't backed up, unless your intention is to mimic the original server in nearly every way.
Go to Top of Page

clarkbaker1964
Constraint Violating Yak Guru

428 Posts

Posted - 2004-09-27 : 14:34:02
Agree Completely especially considering you are going from one version to another...
Check out DTS packages, moving User id's...

Their is a command in the dts that will help you do this...


Surf On Dude!
Go to Top of Page

revolution9
Starting Member

2 Posts

Posted - 2004-09-27 : 15:58:53
Thanks for the posts.

I have just successfully restored MASTER to the new server and have completed the upgrade so far to SQL 2000 sp2. Everything seems to be working very well.

I did take the steps to make sure the server was built to the same specs as the originating server and I know this helps a lot.

I would honestly prefer to do everything with the scripts but I just don't have the practice with them to do it correctly and I don't like practicing on the client site.

Thanks again
R9
Go to Top of Page
   

- Advertisement -