web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Issues moving from On-...
Microsoft Dynamics NAV (Archived)

Issues moving from On-Premise to Azure SQL

(0) ShareShare
ReportReport
Posted on by Rupert West 124

I have recently moved my NAV 2016 to a Test Cloud environment and have the database on Azure SQL but am having issues with the Database collation.

Within the NAV Administration whenever i change the Database credentials to SQL Authentication and apply it is stating that the database is using an unsupported collation - 'SQL_Latin1_General_CP1_CI_AS' and prompting to use the development environment to change it.

However - when i open the database in the Development envrionment i'm prompted that the server requires a 'Per Databse License to be opened on SQL Azure'

I did try to run the powershell to Import the NAVServerLicense to rectify this error but the NAV Server will start and then stop within 60 secs.

Any guidance would be most appreciated

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Stefano Demiliani Profile Picture
    Stefano Demiliani 37,166 Most Valuable Professional on at

    Not so clear what is your problem. Changing the collation of a previously created Azure SQL Database is not possible. You can do that by exporting a BACPAC file, restore it on an on-premise SQL, change here the collation and then restore the BACPAC to Azure SQL.

    Regarding the license problem: have you imported a development license?

    Import-NAVServerLicense DynamicsNAV100 -LicenseData ([Byte[]]$(Get-Content -Path “C:\Licenses\NAV_2016_DEV.flf” -Encoding Byte)) -Database 2

  • Verified answer
    Rupert West Profile Picture
    Rupert West 124 on at

    Stefano,

    Thanks for the reply.

    I had originally Exported the On-Premise DB using a BACPAC file to an Azure Storage Account and then Imported it into an Azure DB.

    When i imported it i seemed to accept the default collation so i've deleted the DB and re-imported it using the same collation as the On-Premise DB had.

    Hopefully this will resolve the issue.

    Thanks for making me re-trace the import

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
HoangNam Profile Picture

HoangNam 7

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans