Upgrading SQL 2005 32bit to SQL 2012 64bit - replacing single domain server

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 SP4 SSIS 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).
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.
Mark Lytleowner operatorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
1) Would having SQL installed on the old server affect the migration of the domain and all its parts?

2) Do you have or can point me to this task specific set of steps or a guide?
First, you should run the SQL Server 2012 Upgrade Advisor on the SQL Server 2005 databases so it will check for any compatibility issue. For those databases that the report didn't find any issue you can detach them from the SQL Server 2005 and copy the correspondent data and transaction log files to new the server add attach them to the SQL Server 2012 instance. After that the first thing you'll need to do is to change the database compatibility level from 9 to 11 (2005 to 2012).
Don't forget to transfer the SQL Server logins from the old to the new instance. This MSDN article shows how to do it.
Migrating SSIS packages may be more complicated to perform but that depends on the complexity of the packages.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mark Lytleowner operatorAuthor Commented:
Thank you Vitor, this will either take place by mid-week this week or mid-week next week. Will let you know.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Didn't realize that you also want to migrate SSIS. For that you have the SSIS Package Upgrade Wizard.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

RayData AnalystCommented:
One other note.... Something "out there" in the domain is likely connecting to that SQL Server by name or IP.  You'll need to identify any of those applications, alert the users to the down time while moving DBs, ensure your SQL logins from the SQL 2005 server are transferred to the 2012 SQL box, then point the earlier discovered applications to the new server.

Of course I'm assuming there are applications that people use with that instance of SQL  :-)
Mark Lytleowner operatorAuthor Commented:
Vitor, yes well while poking around in SQL Management studio - I saw the term SSIS.... I will also be consulting with the application support people to get as much as I can from them and will ask 'IF' SSIS is a consideration. In other words - not sure and maybe should ignore that I said that for now. Thanks for the link - I will look at that if SSIS is a consideration.
Mark Lytleowner operatorAuthor Commented:
Thanks Ray,
SQL is needed for a software - Siriusware - and is providing the databases for 'salespoints' - stations where customers are making purchases. This is a seasonal operation and is for the most part shut down until winter. Yes these connect via SQL server name or IP. And thanks for the login move reminder. Will let you know once I get into it. Thanks.
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
One last thing. The Communications from applications to SQL usese as you say IP och Hostname. Might I suggest that you set up a DNS name pointing to the host. The Point being next time you want to move the sql, you only need to restart the applicationservers, no appconfiguration is needed if you use a DNS entry.
When the SQL breaksdown/is outdatet, all you do is move to a new machine (i e Databasese, logins, SQL Jobs etc), and update the DNS entry to this new server (It needs to answer to the same port).
An even bolder suggestion is a DNS entry per application. This gives you the ability to isolate a application, either for errorseeking, or to provide an application with a stronger SQL host.
Regards Marten
Mark Lytleowner operatorAuthor Commented:
Thanks Marten, will look at that in the next week prior to upgrade.
Marten RuneSQL Expert/Infrastructure ArchitectCommented:

Any Feedback?!?
If the solutions are unacceptable, then write that this is the case and the reason. Otherwise you won't get any more proposed solutions, since the experts feels that the case is solved.

Regards Marten
Mark Lytleowner operatorAuthor Commented:
I apologize for not following up. All is good. Thank you for your assist.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.