{"id":12816,"date":"2016-07-14T10:00:17","date_gmt":"2016-07-14T08:00:17","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/nav\/?p=12816"},"modified":"2024-03-05T11:47:16","modified_gmt":"2024-03-05T19:47:16","slug":"database-conversion-dynamics-nav-database-azure","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2016\/07\/14\/database-conversion-dynamics-nav-database-azure\/","title":{"rendered":"Database Conversion for a Dynamics NAV database stored in Azure"},"content":{"rendered":"
One of the nice new features of Microsoft Dynamics NAV 2016 is the ability to place a Microsoft Dynamics NAV database in Azure SQL Database rather than the traditional method of storing it using an on-premises SQL Server instance. For more information, watch\u00a0this video<\/a>.<\/p>\n So, what happens after you move your Dynamics NAV database to Azure SQL Database and the time comes to apply a cumulative update (CU),\u00a0and the CU involves a database conversion process, which\u00a0CU6 did (see \u201cNote\u201d in the Overview section of the KB article for CU6<\/a>)?<\/p>\n You might expect that you could simply open the Dynamics NAV database with the Dynamics NAV development environment and it would convert the database. After all, this is how it has worked for on-premises installations since the dawn of time. However, this process will not work when the Dynamics NAV database resides in Azure SQL Database. If you try to open the database in the with the new version of the\u00a0development environment, you will get the following warning message:<\/p>\n