March 7, 2018 at 4:20 am
Hi all
A bit of an oddball question here. I think the answer is a simple 'yes' but I could do with some confirmation.
I am looking migrate some SQL 2012 databases to SQL 2016. Our software support contractor have stated they would like the data databases to remain in SQL 2012 compatibility verson. They do not manage the servers or SQL engine, just the database structure and programability. I like the feature of multiple tempDB files having improved management in SQL 2016 (not having to manually set trace flags by following notes I don't fully understand).
As the tempdb files are at the engine level, would this impact a data database set to an earlier compatibility level?
Thanks in advance
March 7, 2018 at 4:45 am
Compatibility is just for the query optimiser/query processor when executing query features that have changed across the versions. It's nothing more than that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 7, 2018 at 4:53 am
Many thanks. I can continue with my plan.
March 7, 2018 at 4:59 am
Rather upgrade to SQL 2017, not 2016..
The work in testing and upgrading will be the same.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 7, 2018 at 6:44 am
I have contacted the support company who would perform the testing (as I only handle the server/SQL engine and act as first line regarding technical issues).
Doubt I will get an answer in time (by year end) but I have 2016 & 2017 developer on my test rig.
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply