sql server - Database collation - Change Impact -

i weak far databases concerned so, please bear me. have database in greek.ci_ai working without issue several applications. servers put data db on greek locale.

however, application treats information , checks integrity constraints in case-sensitive manner. have not run issues specific application far concerned may have deal later when data more , impact bigger. proper way this? mean change or should drop , recreate right collation? if not have drop it, how affect data?

comparing 2 have not found differences.

http://collation-charts.org/mssql/mssql.0408.1253.greek_ci_ai.html http://collation-charts.org/mssql/mssql.0408.1253.greek_cs_ai.html

thanks help!

you should not change db collation greek_ci_ai greek_cs_ai/bin. if application checks integrity constraints in case-sensitive manner means business rules require approach , case sensitivity implemented directly in constraints.

if change database collation greek_cs_ai can break application code. if there tables table1 , table2 in database now, code can reference them table1 , table2, once db collation becomes case sensitive, objects table1 , table2 not found.

also, difference between greek.ci_ai , greek.bin

to view eyes, try selects of data adding order col1 collate greek_cs_ai --greek_cs_bin select statement

you'll find in first case uppercase/lowercase letters placed next each other lowercase precede uppercase within same letter while in second(bin) case uppercase letters precede lowercase letters this:

this because bin collation compare characters based on ascii codes.

note there bug in bin collations compare correctly first character of string, reason if ever need use binary collation use bin2 collations have no bug