ktjamms2
asked on
Problem with Lookup Data Flow Component
I'm trying to map available input column (IDno) to available lookup column (IDno) and I get an error "cannot map the lookup column "IDno" because the column is set to a floating point data type
ASKER
I'm not sure I'm following this
<<<<so as a workaround, convert it to a different data type for example sting, and do a lookup against a select statement and convert your column too to the same data type.>>>
Should I change the data type properties in the Advanced Editor for OLE DB Source for the External Columns, Output Columns, OLE DB Source Error Output, or all of the above?
<<<<so as a workaround, convert it to a different data type for example sting, and do a lookup against a select statement and convert your column too to the same data type.>>>
Should I change the data type properties in the Advanced Editor for OLE DB Source for the External Columns, Output Columns, OLE DB Source Error Output, or all of the above?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Can you give me a sample query?
Sure...
look at the last attached pic...what's your query?
look at the last attached pic...what's your query?
ASKER
How would you then handle getting it converted back to the original data type (float) for the upsert?
Please before map make sure the data type of both source and destination columns should be same.
You still can use the Data Conversion Task to get it back...the problem with float that it's not an exact it's approximate ,that's why it's not supported.
ASKER
I'm getting a big huge error with this:
SELECT CONVERT(varchar, IDno) AS IDNOCONVERTED FROM tablename LOOKUP-ERROR-1.docx
Adjust the 50 for your desired results, don't go too much over it :)
Select cast(IDno as varchar(50)) AS IDNOCONVERTED FROM tablename
validate the query first in SSMS and make sure it runs fine, before you use it in SSIS lookup screen
ASKER
It does fine in Server Management Studio, but I'm still getting the error in SSIS. A normal select query runs fine, but when I add the convert it blows up
ASKER
I get the same error using cast
Then convert it to a discrete precision value - such as a decimal, currency, or integral type.
what is that column data looks like anyway? currency or what? can you post examples?
what is that column data looks like anyway? currency or what? can you post examples?
ASKER
It's just a number. I tried this:
cast(IDno as int) as CASTIDno
Getting the same error. I tried parse query and the error reads:
Error in list of function arguments: 'AS' not recognized. Unable to parse query text.
cast(IDno as int) as CASTIDno
Getting the same error. I tried parse query and the error reads:
Error in list of function arguments: 'AS' not recognized. Unable to parse query text.
ok, I'm not sure what to tell you, but there's something wrong with your query.
Anyway as a work around, create a view in the SQL DB since the convert or cast works fine there, as a workaround and it should be faster, then select the VIEW in the lookup.
Anyway as a work around, create a view in the SQL DB since the convert or cast works fine there, as a workaround and it should be faster, then select the VIEW in the lookup.
ASKER
These are dBASE tables that I'm trying to get into a SQL database
Hey Just convert using Conversion task and make sure first trim it.
I'm not really familiar with dBase, but as a work around, create a view in the SQL server that gets it's data from the DBase, then use it in the lookup.
ASKER
Hi PatelAlpesh:
I used the Data Conversion tool and made a copy of IDno with a numeric data type, but when I try to map the copy of ID no to IDno in the lookup tool I'm still getting the same float data type error. Is it because the destination table is still float? I am supposed to use the destination table for the lookup right?
I used the Data Conversion tool and made a copy of IDno with a numeric data type, but when I try to map the copy of ID no to IDno in the lookup tool I'm still getting the same float data type error. Is it because the destination table is still float? I am supposed to use the destination table for the lookup right?
ASKER
The source and destination data types are both float
ASKER
Thank-you!
http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/8dcc2705-51a6-49de-aa5c-d538087059f1
so as a workaround, convert it to a different data type for example sting, and do a lookup against a select statement and convert your column too to the same data type.