July 24, 2008 at 3:00 pm
Has anyone had to move system databases from a Standard Edition to an Enterprise Edition?
We are retiring a server that has SQL Server 2005 Standard Edition and want to move everything to an already built (but not in use) SQL Server 2005 Enterprise Edition server. This requires moving the Master, Model, MSDB databases. Will this work? Are there any 'gotchas' to watch out/prepare for?
-SQLBill
July 24, 2008 at 3:40 pm
Model should be fine. I'd be careful about Master. MSDB should be fine.
Why not install Standard, copy the databases over, then do an in-place upgrade? Is that out of the question here?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 24, 2008 at 3:50 pm
I am being told that doing a new install of Standard and upgrading is not an option. We, the DBAs, do not do the installs here, we have to have the system admins do any installs. However, I am pushing for a reinstall......
One issue is timing....getting an install approved and done takes a while.
-SQLBill
July 24, 2008 at 8:39 pm
systems databases are NOT compatible between editions. backup/restore from/to editions does not work.
* Noel
July 24, 2008 at 10:29 pm
Master really needs logins moved (and roles)
msdb needs jobs, maint plans, etc. moved. You might be able to script all this stuff out.
Model, what needs to be moved?
July 25, 2008 at 9:25 am
Model isn't really a system database. It's a template for user databases.
That's why I say that one should be fine.
MSDB, I wouldn't do a backup/restore, I'd do an insert...select from one to the other. That'll get you most of what you need.
Master is the big deal. I'm not sure what I'd do with that one.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 25, 2008 at 11:09 am
sp_help_revlogin, script out logins, add them back.
Might need to script roles out on the server level, not sure where that's kept in 2005 and how easy it is to pull out.
July 25, 2008 at 3:23 pm
We set up MODEL in very specific ways depending on how the server is to be used. So it needs to be moved with everything else. Let's say ServerA is SS2005 Standard and ServerB is SS2005 Enterprise. The plan right now is to stop services on both servers. On ServerB, change the Master, Model, MSDB, and TEMPDB files to have .old after them so they don't get overwritten. Then copy the Master, Model, MSDB, and TEMPDB files from ServerA and put them in the same location as ServerB's original files. That way when we start up ServerB it will find the new files without changing the startup file. We have done this on all of our previous moves, however, we have never gone from Standard to Enterprise before. It's always been from Standard to Standard or Enterprise to Enterprise. So the concern is....will the Standard Master cause problems on the Enterprise server?
-SQLBill
July 26, 2008 at 11:40 pm
To my experience, Instead of writing huge T-SQL scripts. Its really pain and there may be a possibility to miss some data in the older version.
Please proceed with upgrading the version and edition of sql
Regards,
Venkatesan prabu .J
Thanks and Regards,
Venkatesan Prabu, 😛
My Blog:
http://venkattechnicalblog.blogspot.com/
July 28, 2008 at 7:58 am
Since I haven't tried doing what you're proposing, and don't have a system to spare right now for testing it, I can't say one way or the other whether it will have a problem. I would be kind of surprised if the change in Master does not cause problems, but there's no way to know except by testing it.
It sounds like you've got a good plan for the test. Try it out. Worst that happens is the service won't come up correctly, and you restore the old system DBs.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 28, 2008 at 1:11 pm
yes very important make sure you keep a copy of the enterprise system databases incase you need to bring them back online otherwise you'll need the install cd to repair SQL installation and rebuild the system dbs
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 28, 2008 at 2:00 pm
In place upgrade!
July 28, 2008 at 2:11 pm
kevin.kunz (7/28/2008)
In place upgrade!
That's already been suggested and apparently isn't a viable option.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 28, 2008 at 4:26 pm
Thanks for all the inputs. I am still doing the planning for this (lots of coordination is needed for all the moves) and hope to do the move before the end of August. I'll post what I do and any issues that come up.
-SQLBill
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply