May 3, 2017 at 7:36 am
Guys,
Having a brain hiccup this morning. We're planning a move of SQL 2008 (+ R2) databases to SQL 2012, 2014 + 2016. Vendors support vary from one application to another. Someone (not me) suggested that we could move all the databases to SQL Server 2016, just modify the database compatibility to the appropriate level, whatever the vendor will support. My thinking, yeah, this should work, why didn't I think of it? It took a while to sink in (some things just don't work the way they used to). Why bother with multiple environments, just use the one.
Any issue with this thinking? Comments are appreciated!
May 3, 2017 at 7:47 am
You can upgrade 2008R2 to 2016 although there are a few steps and hoops to consider. Found the following a useful resource
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server
May 3, 2017 at 7:51 am
Oh and I forgot to mention compatibility mode does have its pitfalls while it affects SQL Syntax and Query parsing there are some known issues with strange performance occurring after compatibility mode changes.
May 3, 2017 at 7:52 am
The compatibility levels only make certain things behave like that version, its not a setting to make the 2016 engine behave like the 2008R2 engine for a specific database, the database version will still be a 2016 database.
https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level
May 3, 2017 at 8:08 am
Anthony,
Your URL is not working - "The page you requested could not be found". Do you have an updated link?
May 3, 2017 at 8:25 am
Sorry unsure what happened to that link
Corrected below
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply