We would like to upgrade our existing DB in SQL 2008 to SQL 2016. Below is the plan which we created.
1. Take backup of existing DB in SQL 2008
2. Create a new server with Windows 2016 OS 64 bit
3. Install MS SQL 2016 SP1 Standard in the new server
4. Copy the backup(from SLQ 2008 DB) into the new SQL 2016 Database
5. Run configuration wizard in the Primary polling engine and addition polling engines
6. Check the application functionality
Can some one please review this. We need to know mainly on the restoring of backup from SQL 2008 to SQL 2016.
Is there any issues foreseen in this plan?
I know its old thread but I have questions:
I am planning to upgrade SQL server 2012 to 2016 on the same server ( don't want to migrate on the new server due to some issue) and currently using windows 2012 R2, can we do that?
Is there prerequisite which needs to be followed?
I am also looking to upgrade SolarWinds windows server 2012 R2 to 2016, can we do parallel?
I look forward to your reply.
Your Steps are OK
Last week, I completed this same upgrade from SQL 2008 R2 SP3 to SQL 2016 SP1 with no issues. In my case, it was an in-place upgrade on the same physical server. It must be 2008 R2 SP3 or SP4 to be able to do a direct upgrade to 2016. I did a demo/pilot upgrade first - it was very helpful. Then the new Orion installer is an awesome one run upgrade all module piece - Thanks to SolarWinds for the improved installer.
Your module versions will sure require multiple steps to get to the latest version. I will suggest downloading NPM installer 12.1 and 12.2. It will help upgrade all your other components.
If you use SQL management studio, then download/install version 16.5.3 for the 2016 SQL. version 17.x has issues with the management plan wizard
Hope this helps a bit
Those steps look good don't forget to deactivate your licenses so that you can reactivate on the server also please see KB below for any further tips.
You shouldn't need to de-activate any license if you are just migrating your SQL Server, as the license is for the SolarWinds applications. The specific steps are in this part of the KB
Thanks David for the suggestion. Also the new DB which we plan will be having the below sizing. Can you please tell me if this is the required one.
|Orion DB||32 vCPU, 3.0GHz||128GB||100GB/2.0 TB||Win Server 2016 64bit||MS SQL 2016 SP1 Enterprise|
The modules which we are using is as below.
Latest version available
Around 4000 devices needs to be monitored with this environment. Based on the number of elements to be monitored we will be having 3 additional polling engines also in our environment. Along with this there will be integration with VMan also. Our data retention period is for 1 year.
I would agree, the only thing I would suggest is in terms of NetFlow (NTA) I suspect SolarWinds are about to drop NTA 4x by the end of the month into GA release, and that version has moved onto SQL 2016 server, if you intended to move to that version and wanted to host the NTA DB on the same SQL Server you might just want to spec the storage accordingly and make sure you partition the drives nicely (there are some good guides available).
Otherwise, it all looks good
Yes - The NTA 4.4 (Which is currently in Release Candidate, due to be GA very soon) will require SQL Server 2016 to host the database, SolarWinds are moving away from FastBit. If you don't have SQL2016 then you can stay on NTA 4.2.3 no problem. Just something to consider in your future planning.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.