Which collation choose for SQL Server instance and database? -
I am working on a Windows application based on a database of SQL Server 2008 R2 This application is currently available in Belgian companies. Is sold, which use four languages: English, French, Dutch, German and soon, this application will be sold to other countries in Europe and beyond.
Here are the questions I ask myself:
-
For SQL Server example
- What language to choose?
- Do we want the same option on the sensitivity of the case and the other accents of the database?
- Should be a binary collation?
- Impact on temporary treatment (tempdb)?
-
For the database
- What language to choose?
- Should the location to be used with the Windows Client application take into account?
-
For the development environment and
Thank you for your help. P
When working with a foreign language, or multiple languages If I do CI_AI_SI to prevent any particular character, the issues associated with the character / string field (i.e. inclusion, cast, etc.) As a result, the language should also be unicode. Keeping in mind the different scenarios which you can run in, this is a catch-all scenario.
I can suggest programming in Nauturtha instead of your standard behavior. Yes, the size of the data doubles, but you should help in reducing a strange conversion in your stored procedures.
Comments
Post a Comment