I have been working on databases in a Always On High Availability group which - for reasons that I do not understand - have different default languages for an application's login on the primary and secondary nodes.
The particular situation I have at the moment is this:
- The language that the application expects is British English. It does not specify the language that it uses when it connects; it uses whatever the default language is for the login. The documentation for the application says that the default language should be British English, presumably because it does not specify a language on connecting.
- The application connects to the listener, not to either of the nodes directly.
- The application will often save dates as strings (e.g
UPDATE FooTable SET BarColumn = '01\02\2020' WHERE IdColumn = 42). The data will be saved in a date or datetime column.
- The default language of the login on the database listener is British English.
- The default language of the login on the primary node is British English.
- The default language of the login on the secondary node is American English
I am no DBA, and certainly no expert in Always On High Availability. What dangers might there be/have been in using this configuration? Does it matter if the languages on the primary and secondary nodes are swapped?