Cannot resolve the collation conflict on Azure between master database and db
-
We have an Azure datanbase which up to today has been working fine
However after our latest deployment, we are unable to run our
application connected neither can I connect Azure Data Studio - Profiler to the
Azure database.
I get the following error message:
Cannot resolve the collation conflict between "Latin1_General_CI_AS"
and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation
Now when I look at Azure.. i see that there is a difference in Collations
as shown in this screenshot...
Im baffled because nothing should have changed the collation on the master
database on Azure
When i look at the Azure portal, the Collation sequence for the database
on Azure is Latin_1_General_CI_AS
Other information:
We are deploying the database using SQLPackage
What could have cause the collation to change on master to be different?
Could it have been setting the
Also how can i change the collation for the Azure master or Logger_Groups_CI
database to match each other
Because you cannot change collations on azure
-
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
-
It looks like you are using PaaS. It is better to rollback and restore the DB to an earlier state as it was before this deployment.
Check this URL:
https://www.sqlshack.com/how-to-change-an-azure-sql-database-collation/
Also redeploy in a test environment to correct the collation first and then work on production.
=======================================================================
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply