Best Practice upgrade SQL 2008 standard to 2019 standard
I need to upgrade my current SQL Server 2008 standard to sql 2019 standard. Need step by step instructions. I am not a DBA. I am using a Hyperv 2012r2 server to host.
Thank you in advance.
Thank you in advance.
ASKER
Would like to do an inplace upgrade, but since we are going from 2008 to 2019, is why i was asking the question. The database is about 400GB and is used in Electronic Medical Records. I want to have the least amount of downtime as safely as possible.
From the Info you provided I can't do an inplace. I can do a side by side or a migration. Because of other software for my EMR is installed and maintained by Eclinical works I would like to be able to have the finished product on the production server. I don't know what the difference between a side by side and a migration. I do have another hyperv server to use as a test enviroment.
From the Info you provided I can't do an inplace. I can do a side by side or a migration. Because of other software for my EMR is installed and maintained by Eclinical works I would like to be able to have the finished product on the production server. I don't know what the difference between a side by side and a migration. I do have another hyperv server to use as a test enviroment.
For the downtime, just use your Hyper-V infrastructure. Create a separate SQL Server 2016 instance. Restore the backup. Create a new backup. Restore the backup on your SQL Server 2019 instance.
Inplace would mean an upgrade to 2016 first, then an second upgrade to 2019.
btw, on what host does it currently run? And did you already test your applications with 2019?
Inplace would mean an upgrade to 2016 first, then an second upgrade to 2019.
btw, on what host does it currently run? And did you already test your applications with 2019?
ASKER
The Host is a 2012r2
The ECW enviroment consists of 4 windows 2012r2 VM servers.
1) Application Server (tomcat)
2) Database Server - MS SQL
3) Reporting Server -
4) Interface Server - HL7 data transfers
ECW Supports upto SQL 2017, but am inquiring as to if they have tested 2019
On these VM's since they host such critical data, only have applications ECW has installed.
basically they maintain the software, I maintain the hardware and infrastructure, backups etc.
As I am writing this ... might be best to buy SQL 2016 on ebay (since its an inplace upgrade) and use that for a couple of years til end of life, then upgrade to 20xx. That could keep down time to a minimum. Thoughts?
The ECW enviroment consists of 4 windows 2012r2 VM servers.
1) Application Server (tomcat)
2) Database Server - MS SQL
3) Reporting Server -
4) Interface Server - HL7 data transfers
ECW Supports upto SQL 2017, but am inquiring as to if they have tested 2019
On these VM's since they host such critical data, only have applications ECW has installed.
basically they maintain the software, I maintain the hardware and infrastructure, backups etc.
As I am writing this ... might be best to buy SQL 2016 on ebay (since its an inplace upgrade) and use that for a couple of years til end of life, then upgrade to 20xx. That could keep down time to a minimum. Thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thats always the case. Matter of fact they suggested this upgrade. Thanks for the info. Its great to have a sounding board. When your the only guy in the IT dept its good to have a resource to fling ideas at.
You need to upgrade to 2016 first, then to 2019.
The question is do want a in-place upgrade or - as you mentioned Hyper-V - do you want to setup a new server?