One somewhat obscure issue you might encounter when upgrading from a legacy version of SQL Server to SQL Server 2016 or later is a change to how some data type conversions are handled. Microsoft describes it like this:<\/p>\n

\n

\u201cMicrosoft SQL Server 2016 and Microsoft Azure SQL Database include improvements in data type conversions and in several other operations. Most of these improvements offer increased precision when you deal with floating-point types, as well as with classic datetime types.\u201d<\/p>\n<\/blockquote>\n

This changed behavior only comes into play when you are running on database compatibility level 130 or later, and it only affects persisted objects (such as persisted computed columns, filtered indexes, indexed views, and indexes that use computed columns).<\/font><\/p>\n

Because of this potential issue, Microsoft recommends that you do some additional validation checking on your legacy databases before you change their compatibility level to 130 or higher to find out if you might be affected by these changes.<\/font><\/p>\n

Here are the steps for the validation and correction process:<\/font><\/p>\n

\n
1. Restore the legacy database to SQL Server 2016 or later instance in your test environment<\/font><\/li>\n
2. Enable global trace flag 139<\/font><\/li>\n
3. Run DBCC CHECKDB WITH EXTENDED_LOGICAL_CHECKS, NO_INFOMSGS, TABLERESULTS<\/font><\/li>\n
4. Disable global trace flag 139<\/font><\/li>\n
5. Change the compatibility level of the database to 130 or later<\/font><\/li>\n
6. If Step 3 reveals any issues, then rebuild the objects that it identified<\/font><\/li>\n<\/ol>\n

   Microsoft has more detail about this change here<\/a>. Personally, I think this just another step that you should add to your testing plan during an upgrade project.<\/p>\n

    <\/p>\n

   Additional Resources<\/font><\/u><\/strong> <\/p>\n

   My new Pluralsight<\/a> course, SQL Server: Upgrading and Migrating to SQL Server 2016<\/a> has just been published. This is my eleventh course for Pluralsight, but the complete list of my courses is here<\/a>. <\/p>\n

   Building on this online course is a new three day class, IEUpgrade: Immersion Event on Upgrading SQL Server<\/a>, taught by myself<\/a> and Tim Radney<\/a>. The first round of this course will be taught in Chicago from October 11-13, 2017. <\/p>\n

   Finally, I will be presenting a half-day session called Migrating to SQL Server 2017<\/a> at the PASS Summit 2017<\/a> in Seattle, WA from October 31- November 3, 2017. You can use this code: BL150GG to register for the PASS 2017 Summit to get a $150 discount. <\/p>\n

   Here is a link to the complete series<\/a> about upgrading SQL Server.<\/p>\n","protected":false},"excerpt":{"rendered":"

   One somewhat obscure issue you might encounter when upgrading from a legacy version of SQL Server to SQL Server 2016 or later is a change to how some data type conversions are handled. Microsoft describes it like this: \u201cMicrosoft SQL Server 2016 and Microsoft Azure SQL Database include improvements in data type conversions and in […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[246,342,353],"tags":[350,352],"class_list":["post-1266","post","type-post","status-publish","format-standard","hentry","category-sql-server-2016","category-sql-server-2017","category-upgrading-sql-server","tag-upgrading-to-sql-server-2016","tag-upgrading-to-sql-server-2017"],"yoast_head":"\n