SQL collation for Citrix products
I recently received an email asking me about which collation should be chosen for Citrix products. Here is a table of SQL collations by product. I’ll try to keep this post up to date.
Don’t hesitate to help me to improve this table.
| Product | Collation |
| XenApp (6.5) | Latin1_General_CI_AS |
| Storefront | latin1_general_CI_AS_KS |
| Provisionning Services | SQL_Latin1_General_CP1_CI_AS |
| XenDesktop (5.6 to 7.1) | Latin_General_CI_AS_KS. |
| Edgesight | Latin1_General_CI_AS. |
| XenMobile | Not found for now. PostgreSQL database automatically created with installation Wizard but possible to choose Microsoft SQL (with no other explanation on eDocs). |
| XenApp & XenDesktop 7.5 * | Latin1_General_CI_AS_KS. Latin1_General could change depending contry. It could be Japanese_100_CI_AS_KS. |
About Author
jeemroq
Comments
Does it matter if the SQL Server collation is different to the collation of the database? If it is it means the database can’t import/export data to/from the TempDB
Citrix doesn’t specify if instance collation has to be the same, but I prefer to be cautious. So, I never tried to go with different collation and I’m not sure Citrix needs TempDB. I would be interested in your tests results if you try different collations.
I had a reply from Citrix support…
XenDesktop database MUST have collation _CI_AS_KS i.e. Case Insensitive, Accent Sensitive, Kana Sensitive Ideally the SQL Server (instance) would have the same collation as all user databases BUT this is not always possible – so it is supported even when Collations don’t match but XD database MUST BE CI_AS_KS!
The server collation is not that important although there might be an issue when utilizing TEMP database
On your example your instance is _CI_AS. There will be no issues with the TEMP database as the instance is Case Insensitive.
Please let me know if you have any further queries.