The way its setup right now, our DNN installation uses forms authentication for the website. But SQL Server is using a common SQL Login for everyone. Thus the database is still returning dates, errors, etc in English.

Is there a way to tie SQL Server connections into the forms authentication model so that the SQL Server connections match the locale of the user logged into the website?

If not, what are some of your solutions to getting SQL Server to recognize the locale of the logged in user when using forms authentication?

We have thought of always setting the "SET LANGUAGE Language" before each database command... but we would like to hear some more input on other alternatives.

Thank you

We are trying to avoid future issues in our custom modules. Right now we do not have any multi-culture support for anything. I didn't mean to imply I care about the error messages, we do not pass the SQL error to the user. Ideally I will use "set dateformat dmy" instead of "set language Spanish" for example

The problem is we pass date strings straight into SQL, and SQL is expecting a USA DateTime (mdy) but a spanish string (dmy) is being passed in from the date picker on the screen: SQL throws conversion error.

Yea, we should have written our code differently to not pass strings into SQL.

Is there any clever way to get SQL to recognize the PreferredLocale of the DNN user?