March 15, 2025 at 4:35 pm
I have read that the collation at the instance level cannot be changed. I am guessing that statement is correct. I am thinking about uninstalling the instance and reinstalling it with the correct Collation but I thought I'd ask the experts 1st.
This is the error I am seeing during our test deployment before we go to Prod.
I am seeing this error
ODBC Driver 17 for SQL Server. Cannot resolve conflict between "SQL_LATIN1_GENERAL_CP1_C1_AS" and "LATIN1_GENERAL_BIN" in the equal to operation
However, I checked sys.databases and all system databases are SQL_LATIN1_GENERAL_CP1_C1_AS" and all user databases are LATIN1_GENERAL_BIN
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
March 15, 2025 at 5:26 pm
I ended up following instructions on this video which solved the issue
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy