I got caught by another localizaion feature of SQL Server today.
SQL Server is not aware of regional settings.
SQL Server is not aware of regional settings.
This can be a real pain. If your machine uses say German regional settings and your database returns 1.01 if you use variant conversion routines (hey I am still using ado – we all can’t be on the bleeding edge) this can arrive as 101
This is not what is wanted. This has brought me to question where in a data access layer should the localization go?