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.

Thanks
LVL 2
Zoldy2000Asked:
Who is Participating?
 
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:
https://www.experts-exchange.com/articles/18644/SQL-Server-database-migration-The-Detach-Attach-method.html
https://www.experts-exchange.com/articles/18667/SQL-Server-database-migration-The-Backup-Restore-method.html
https://www.experts-exchange.com/articles/22159/SQL-Server-database-migration-The-Copy-Database-Wizard-method.html

About the question of maintaining the same server name and IP, it works if you don't bring online both servers at same time.
0
 
David Johnson, CD, MVPOwnerCommented:
with local user accounts maybe, domain accounts not. won't affect sql login accounts.
0
 
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.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
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.
0
 
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.
0
 
Zoldy2000Author Commented:
Exactly what I needed
0
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.

All Courses

From novice to tech pro — start learning today.