SQL Server String comparison Time Zone case-insensitive Method

By default, SQL Server is case insensitive, such as userName.

SQL Server is case insensitive by default, such as userName =

By default, SQL Server is case insensitive. For example, userName = 'jesse 'and userName = 'jesse' have the same results. When verifying the password, you may need to be case sensitive to the string. You need to perform some processing to introduce two methods:

Method I: Convert to binary before comparison, because the case-sensitive ASC code is different. For example:

Method II: sorting rules are also based on binary. Add collate Chinese_PRC_CS_AS_WS to the field

For example:

Case sensitivity is related to sorting rules. The meaning of each part of the sorting rules is as follows:

Example: Chinese_PRC_CS_AI_WS

First half: the UNICODE character set. The Chinese_PRC _ pointer sorts UNICODE in simplified Chinese characters.

The second half of the sorting rule is the suffix meaning:

_ BIN binary sorting

_ CI (CS) is case sensitive, CI is case insensitive, and CS is case sensitive

_ Whether AI (AS) distinguishes stress, AI does not distinguish,

_ KI (KS) indicates whether Kana is distinguished. KI is not distinguished, and KS is distinguished.

_ Whether WI (WS) is differentiated by width WI and WS

Case Sensitive: select this option if you want to make the comparison between uppercase and lowercase letters different.

Accent differentiation: select this option if you want to treat the comparison as different from the accent and non-accent letters. If this option is selected, the comparison also treats the homophone with different accents as unequal.

Kana differentiation: select this option if you want to treat Katakana and katakana as different Japanese syllables.

Width differentiation: select this option if you want to make the comparison between halfwidth and fullwidth characters.