是否可以将SQL Server SQL_Latin1_General_CP1_CI_AS安全地转换为Latin1_General_CI_AS？ [英] Can SQL Server SQL_Latin1_General_CP1_CI_AS be safely converted to Latin1_General_CI_AS?
问题描述
我们有一个旧数据库，其中某些（较旧的）列使用 SQL_Latin1_General_CP1_CI_AS，而最近的更改使用了 Latin1_General_CI_AS。
We have a legacy database with some (older) columns using "SQL_Latin1_General_CP1_CI_AS" and more recent changes have used "Latin1_General_CI_AS".
由于需要联接，这很痛苦
This is a pain as joins need the additional COLLATE statement to work.
我想将所有内容都添加到 Latin1_General_CI_AS中。从我可以收集到的信息来看，它们几乎是相同的排序规则，在此过程中我不会丢失数据...
I'd like to bring everything up to "Latin1_General_CI_AS". From what I can gather they are more or less identical collations and I won't lose data during this process...
有人知道这种情况吗？
推荐答案
此MSDN论坛上有更多信息：
There is more info on this MSDN forum:
哪个州：
如果排序规则是SQL_Latin1_General_CP1_CI_AS或Latin1_General_CI_AS，则应该看不到什么区别，但是两者都有比其他实例更快或更慢的实例。
You should see little difference if the collation is SQL_Latin1_General_CP1_CI_AS or Latin1_General_CI_AS, but both have instances where they are faster or slower than the other.
Latin1_General_CI_AS：-拉丁语1-常规，不区分大小写，重音符号-
敏感，假名类型不敏感，宽度不敏感
Latin1_General_CI_AS :- Latin1-General, case-insensitive, accent- sensitive, kanatype-insensitive, width-insensitive
SQL_Latin1_General_CP1_CI_AS：-拉丁语1常规，不区分大小写，
a对于Unicode
数据，区分大小写，不区分假名，对宽度不敏感，对于非Unicode数据，SQL Server代码页1252上的SQL Server排序顺序52
SQL_Latin1_General_CP1_CI_AS:- Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data
因此，我认为您应该不会有什么不同，尤其是如果您的数据仅为a-z0-9
Therefore in my opinion you shouldn't see a difference, especially if your data is only a-z0-9
这篇关于是否可以将SQL Server SQL_Latin1_General_CP1_CI_AS安全地转换为Latin1_General_CI_AS？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
