With the release of Microsoft’s SQL 2016, one might seriously consider challenging the status quo. An increase of $254 (3.6% increase) per core as compared to SQL 2012 will be considered chump change in comparison to the amount of risk you can mitigate by being on this version. Heck, you may even ask management to take it out of your paycheck. There are at least 5 Reasons to Execute a SQL 2016 Upgrade.
If you champion this project, you get much more than a box of chocolates. For starters, SQL 2016 is now 100% 64-bit. There is no longer a dependency on .NET Framework 3.5. Also, SQL Enterprise Edition is no longer needed if you want to use Availability Groups. Microsoft’s goal is to get rid of database mirroring for good, thereby saying adios to the unreadable single secondary.
Schedule Ad Hoc
The schedule of this task greatly depends upon your timetable. Contact us to get this project on our production schedule.
Estimated Time 60 Hours
We’ve implemented this recently for a multi billion dollar company. Including planning, meeting & training sessions, it took us 60 hours.
Estimated Cost $4,620