In English, the decimal symbol is ".". In european languages such as Germam/italian, it is ",".
Even though BCP has an option (-R) to use regional settings, the decimal symbol is not taken into account even when using this setting to load DECIMAL and/or FLOAT data.
One would expect that an option to "use regional settings" would use ALL relevant regional settings.
Even though BOL mentions implicitly that this is not available ("-R Specifies that currency, date, and time data is bulk copied into SQL Server using the regional format defined for the locale setting of the client computer.", http://msdn.microsoft.com/en-us/lib...802.aspx),
this still seems like missing /not supported.
So far I have come across known bug/hot fix for SQL Server 2000, but seems like the problem still persist in SQL 2005 or higher.
-Possible Hotfix for the -R support http://support.microsoft.com/kb/292648
BCP with format file and -R ignores regional settings http://support.microsoft.com/kb/293155
Does anybody know of any hot fixes /solution that would apply in this scenario that applications can leverage to workaround this problem?
Is there any option to prep the format files such that it can process the decimal "comma" properly, as it should be handled automatically by BCP/SQL Server.