SQL Server sorting rule conflict

The name of a sorting rule consists of two parts. The first half is the character set supported by this sorting rule.
For example:
Chinese_prc_cs_ai_ws
The first half is the Unicode character set. The chinese_prc _ pointer sorts Unicode characters in simplified Chinese characters by pinyin.
Chinese_prc_stroke indicates sorting by strokes of 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-insensitive/case-sensitive)
_ Whether AI (AS) is stress-sensitive, AI is not differentiated, and as is (accent-insensitive/accent-sensitive)
_ KI (KS): whether Kana is distinguished. KKI is not distinguished. KS is distinguished (kanatype-insensitive/kanatype-sensitive)
_ Wi (WS): whether to differentiate width without wi; WS (width-insensitive/width-sensitive)
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,
Comparison also treats letters 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.

I always report errors when executing the stored procedure.

The sorting rule conflict between "chinese_prc_ci_as" and "chinese_prc_ci_as_ks" cannot be solved in the equal to operation.

The reason is:

The server level is higher than the database level, while the server sorting distinguishes Kana.

Therefore, in the stored procedure, create table # tbstationrainvalue (stationno varchar (16) Collate chinese_prc_ci_as, rainvalue float)

Force cancel Kana sorting

Dear friends, I am a cainiao and want to learn programming.