Question:
I import an excel table into mssql using ssis. This table contains float values, separated by a period. Accordingly, when importing data, ssis does not understand that it is a float and writes it as a string. If you use a converter, it just falls out with an error. It is not an option to change regional settings, since in other registries the separator is already a comma. The option to Replace period with comma in the registry before import is fine, but maybe there is some alternative solution?
Answer:
The option with Replace period with comma in the registry before import is not suitable.
Why? This is a very common solution.
You can make sure that sql.ru has already found out that there is no other way in t-sql. How do I force SQL Server to dump numeric data with commas instead of periods?