Timeline for SQL Server default collation vs database with different collation - potential problems?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2019 at 7:51 | comment | added | Solomon Rutzky |
@VoonArt You are welcome. But, can you please clarify what "trying to figure out UTF-8 is working in UCS-2" means? Those are two different encodings so that doesn't really make much sense. Are you using SQL Server 2019 and the new UTF-8 collations? If you are, and are mixing UTF-8 with either NVARCHAR or VARCHAR with non-UTF8 collations, then that is one of the situations I mentioned that could result in data loss. Please update the question to specify exactly which collations (their exact names) are "X Collation" and "Y Collation". Thanks!
|
|
| Jun 7, 2019 at 7:45 | comment | added | VoonArt | Thanks, right now I am trying to figure out UTF-8 is working in UCS-2 :P Its not easy topic. | |
| Jun 7, 2019 at 7:44 | vote | accept | VoonArt | ||
| Jun 6, 2019 at 7:33 | history | edited | Solomon Rutzky | CC BY-SA 4.0 |
added clarification
|
| Jun 6, 2019 at 7:11 | history | edited | Solomon Rutzky | CC BY-SA 4.0 |
added info about what collations at various levels do
|
| Jun 6, 2019 at 6:49 | history | edited | Solomon Rutzky | CC BY-SA 4.0 |
added clarification
|
| Jun 6, 2019 at 6:28 | history | answered | Solomon Rutzky | CC BY-SA 4.0 |