SQL Server 2008 upgrade to SQL Server 2017 standard editions

We are in need of upgrading our SQL server.     I plan on building a new one and migrating and have a few questions.     Once I build the new SQL server and get it updated etc.     How do migrate all the data, user account, and maintenance plans?      Is there a guide or document for this process.     My fear of migrating versus upgrading is that something is missed.        Second question is once everything is migrated does changing the server name and IP address cause any issues.      I want the server name and IP to remain the same as it is now.   Which means once the old server is shutdown I would need to rename the new.

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.

David Johnson, CD, MVPOwnerCommented:
with local user accounts maybe, domain accounts not. won't affect sql login accounts.
Vitor MontalvãoMSSQL Senior EngineerCommented:
I've wrote 3 articles with different methods for migrating SQL Server databases. If you follow them you shouldn't have any problem:

About the question of maintaining the same server name and IP, it works if you don't bring online both servers at same time.

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
Zoldy2000Author Commented:
thank you very much of these methods do you recommend one over the other for simplicity.    I only manage one SQL server so certainly not an expert.    Looking for simple versus fast.
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.

Zoldy2000Author Commented:
sorry if this is a silly questions but I read the articles and copy database seems to be best for me.     But since none of these copy the system databases I asked myself do I even need to copy the system databases?    What do I lose if I don't.
Vitor MontalvãoMSSQL Senior EngineerCommented:
No, no. Do not copy system databases. They are meant to be used only by their own SQL Server instance.
You can migrate the SQL Logins as indicated in my articles and if you have SQL Agent jobs to migrate, you can just script them and have the script run in the new SQL Server instance, as instructed here.
Zoldy2000Author Commented:
Exactly what I needed
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

From novice to tech pro — start learning today.