February 11, 2009 at 11:09 am
Hi,
I have a server that the regional settings are English USA. My actual location is Germany and the client workstation that have SSIS installed on them and from where the development is being done have XP in German and the regional settings are set to German (decimal pointer is comma and not period).
Loading data from a teradata external database into my SQL database from the client desktops has a problem of loosing the decimal point and the values are not correct in the SQL database.
When loading directly from the Server with English US setting this problem does not occur.
Does anyone know if I can work this way or do I need to change the regional setting language and settings to German (which I really don't want to do!)?
Is there any work around that can be used?
Thanks
Shai
February 12, 2009 at 8:12 am
I've just started learning SSIS and had a problem with dates and it came down to setting the locale on the data flow components.. The pitfall is this is hard coded into the SSIS package, but it may be all you need?
February 13, 2009 at 3:58 am
I have already tried that, it does not work...
What is the purpose of LocaleID anyway?
Shai
February 13, 2009 at 4:18 am
It interprets/formats data like dates and possibly float/decimals in a certain way.
I can't remember the full details but you can look up BOL, but it definitely can affect the way dates are interpreted in the data.
If the incoming text file/excel file is formated in mm/dd/yyyy this is generally a US format on dates
UK/Australian dates usually use dd/mm/yyyy for the date format as an example
I guess the only way to resolve the data instead of using the locales is to use the derived columns(?) data flow component or whatever the conversion data flow component is to check the data based on the relevant conditions that you know of and format it from there. The worst case scenario is to convert the data into standard format or something in an ExecSQL task if it is coming from a database, or in the scripting component *shrug* These are things one would probably have done done as an option in SQL 2000 DTS
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply