Sql-server – What are the factors to consider or to worry when we migrate to SQL Server 2017 from 2012

sql serversql-server-2012sql-server-2017

We have been asked to migrate to SQL Server 2017 from 2012. Only coding experience as background we are not so aware of what are the crucial points to consider or to worry when migration.

Some of the points I'm concerned are:

  • Is there is anything missing in 2017 which was working fine in 2012.
    Missing in the sense of an upgrade in 2017.

  • Can we restore a backup
    from 2012 in 2017

  • Also is there is any chance of any kind of data truncation or something like that if we restore DB backup from 2017 into 2012 (If restoration possible)

Best Answer

  1. https://docs.microsoft.com/en-us/sql/database-engine/deprecated-database-engine-features-in-sql-server-2017 as a list of deprecated features for 2017.
  2. 2012 to 2017 yes. 2017 to 2012 no.
  3. No, because you can't restore from 2017 to 2012.

The main thing to look at with your current database is what Compatibility Level is it set to in the 2012 instance? If it's below 110, and needs to stay below 110, then it won't function correctly, or at all.

The only way you'll be able to definitively determine what won't work is install a copy of SQL Server 2017 somewhere (with the appropriate licensing), restore your database to that new instance, and then start testing your application connecting to that new database.

Related Question