Timeline for Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2021 at 22:19 | comment | added | Solomon Rutzky | Chickoo: were you ever able to resolve this? Did my answer below help? Please provide some feedback to let us know the current status of this issue. Thanks. | |
| May 19, 2021 at 15:25 | history | edited | Solomon Rutzky |
edited tags; edited tags
|
|
| May 19, 2021 at 14:29 | answer | added | Solomon Rutzky | timeline score: 2 | |
| May 18, 2021 at 18:10 | comment | added | J.D. |
Is your master database (and furthermore your instance) set to the Latin1_General_CI_AS collation?
|
|
| May 18, 2021 at 17:26 | comment | added | AMtwo |
The msdb110_upgrade script should never throw errors & prevent startup. (However, I have seen quite a few problems with the latest CUs and this script.) I'd suggest opening a case with Microsoft.
|
|
| May 18, 2021 at 16:36 | history | asked | Chickoo | CC BY-SA 4.0 |