July 5, 2015 at 12:43 pm
Hello,
New here and hoping for some much needed direction. We have a single Server 2003 Standard 32bit - 2 core server as a stand alone domain controller - just the one. We have to replace it with server 2012 R2 Standard 64bit server - migrating it into the domain role and removing the old 2003 server. I am not a SQL guy... and it appears daunting.
We have SQL 2005 32bit on the 2003 server with all the business data in it etc... no idea how it was originally licensed. About 25 users in AD. We have a new 2012 server and the new SQL 2012 installation media, licensed for 4 cores, the number of new server cores.
I wish to take the path where I add the new server to the domain and promote it / demote the old - migrate the AD and all other tasks - and have what I need for that. Its the SQL upgrade path that I need assist with. I have some instruction from MS as to migrating the server - but they specify 'no SQL installed on the old server'. I want to get the 2005 SQL into the 2012 with full 2012 functionality (as opposed to an article I read that mentioned being limited to 2005 functionality in 2012 if done a certain way).
Questions:
1) Would having SQL installed on the old server affect the migration of the domain and all its parts? Should I worry about SQL 2005 affecting that?
2) Do you have or can point me to this task specific set of steps or a guide?
I looked at a couple search hits here on this - but they aren't specific enough to my situation.
Any and all input would be greatly appreciated here.... am a rookie with SQL... Thank you.
July 6, 2015 at 3:48 am
Hi alpenit,
Best option for you should be to perform a side-by-side migration. Basically, you have to install a new Windows OS with a SQL Server and then migrate all instance level system objects (logins, tasks, etc.) and finally backup/restore the DBs. There is a fully detailed migration whitepaper here:
https://msdn.microsoft.com/en-us/library/dn144931.aspx%5B/url%5D
It is highly recommended not to install SQL Server on an AD Domain Controller so it would be better to use another server to host the new DC. You can use a temporary VM and then reinstall the legacy Windows 2003 server.
July 6, 2015 at 3:54 am
the server you're putting sql server onto, is it a domain controller
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 6, 2015 at 8:48 am
Yes, we are replacing the old 2003 standard server 32bit with the new 2012 R2 standard server 64bit - the new server will replace the old as the one domain server.
July 6, 2015 at 8:55 am
Let me say more... this new server is to assume the same role as the old - the same domain and all that went with it. The old server uses an application that requires SQL and that application will also be upgraded on the new server - it also requiring the new SQL version, going from SQL 2005 to SQL 2012.
My first hunch is that the migration from old to new SQL might take place after the new server is added to the domain, and eventually promoted as domain controller, the old server being demoted but not removed from the domain - that at this point, is when I would move/upgrade SQL.... but then I am just assuming and don't really know yet. Thanks.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply