Hi,
I have a client from Taiwan who requires a database collation of Chinese_Taiwoan_Stroke_CI_AS. I know everything should be fine internally with the database if I make this setting, even if the SQL Server Instance that it is installed on has a collation of SQL_Latin1_General_CP1_CI_AI; however, I'm wondering if any complications could come into play in other areas, such as if they interact with TempDB or anything else I may not be thinking of, where a collation that is different from the SQL Instance that it resides on could cause problems.
Does anyone know if any problems could arise anywhere, which would instead urge us to just install a separate SQL instance with that collation?
-Ovatvvon :-Q
I have a client from Taiwan who requires a database collation of Chinese_Taiwoan_Stroke_CI_AS. I know everything should be fine internally with the database if I make this setting, even if the SQL Server Instance that it is installed on has a collation of SQL_Latin1_General_CP1_CI_AI; however, I'm wondering if any complications could come into play in other areas, such as if they interact with TempDB or anything else I may not be thinking of, where a collation that is different from the SQL Instance that it resides on could cause problems.
Does anyone know if any problems could arise anywhere, which would instead urge us to just install a separate SQL instance with that collation?
-Ovatvvon :-Q