How do I move EVERYTHING from an old SQL 2008 server to a new physical machine with SQL 2008?

We have some new hardware that we are putting in place to replace the physical hardware of our old SQL 2008 machine. The new machine has a fresh installation of SQL 2008 (same version as the old machine).

What is the recommended way to migrate all tables, users, SQL agent, ... everything... from the old SQL server to the new one?

Who is Participating?
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.

Peter HutchisonSenior Network Systems SpecialistCommented:
You will need to move databases, users, permissions, logs, jobs, alerts, operators and any DTS packages to the new server.
A more details step by step guide is here:

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
Scott PletcherSenior DBACommented:
Make sure the new machine has exactly the same SQL Server version and sub-version as the old machine.

Then backup and restore all your databases (except model (unless you've customized model a lot)), in this order:
1) master (requires special steps, including stopping and restarting SQL)
2) msdb (may not require stopping and restarting SQL, but I'd do it if you could)
--Don't worry after that if user dbs show errors/warnings in SSMS.
3) user dbs.
Scott PletcherSenior DBACommented:
You can also try the "overlay" method of replacing the master db.

Shut down the new SQL.  
In the old SQL, temporarily modify the old master file locations for model and tempdb to match the new server.  Stop SQL.  Copy the master and model files to the new server.
Start the new SQL.  If it comes up OK, you're good, and can go on restoring or attaching user databases.
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

dbrenneckeAuthor Commented:
OK. I will look to try this out shortly.... But, before I do, I have an additional question.

While the SQL versions are identical, the product is different, i.e. going from Enterprise to Standard. Does that have any influence on these recommendations?
Peter HutchisonSenior Network Systems SpecialistCommented:
Enterprise versions are usually used for things like Clustered SQL servers, data warehousing, indexing, snapshots etc  and other advanced features. So, you need to check if any of those features are used and whether you can live w/o them.
dbrenneckeAuthor Commented:
Right.. The only thing we use is clustering with 2 nodes, which is supported by Standard.
Scott PletcherSenior DBACommented:
>> While the SQL versions are identical, the product is different, i.e. going from Enterprise to Standard. Does that have any influence on these recommendations? <<

It should not, since the db's internals are the same (at least as I understand it) no matter which edition of SQL is being used.
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 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.