December 27, 2016 at 8:06 am
So the SQL Server 2008 R2 we have is
Product VersionPatch LevelProduct Edition
10.50.1600.1RTM Standard Edition
Do we need to first upgrade to SQL Server 2008 R2 SP2 and then to SQL Server 2016 ?
or if we plan to upgrade directly from SQL Server 2008 R2 (RTM) it will be re-writing the procedures rather than backup from
SQL Server 2008 R2 (RTM) and restore to 2016 (any edition )
Can we upgrade from 2008 R2 RTM Standard to 2016(Standard or Enterprise )
Thanks!
December 27, 2016 at 9:37 am
I hate in place upgrades. They are asking for problems if there is an issue, and that could happen. If you must, then you need to go to sP2.
I much prefer a side by side upgrade. backup/restore the dbs, script out instance objects.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
December 27, 2016 at 9:46 pm
This was removed by the editor as SPAM
December 28, 2016 at 4:44 pm
+1 on Steve's recommendation for side-by-side upgrade (aka migrate).
Assuming you've done all the necessary prep work and verified your app, tools, scripts, etc... will work with 2016, SxS upgrades lets you prep and verify pretty much everything on your brand new production system before you do the database migration. It is just a bit more work upfront but will likely save you lots later. Just make sure you haven't forgotten stuff in master, msdb and model (if you customized that). If you need to abort the upgrade for whatever reason, reverting to your original 2008r2 instance is quick and easy.
Btw, script it all out instead of using the GUI. That way, the commands you ran and verified in test are the exact same ones you will run for the production system.
Finally, you should really go directly to 2016 SP1, save the effort and downtime from not having to do the update later.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply