From the screen shot, cannot tell whether the problem is with the Read Table or Write Table, but since it ran fine when writing to excel, it's likely the problem is in the Write Table.
Please send the entire log.
Did you try a second step that reads from excel and writes to the second database? That would confirm where the error is.
The mention of parameter 93 is a little strange as you don't have that many columns in the SQL Query or target table.
I think the issue is in the column RECID, which is a BigInt in your source table and an integer in your target table.
How did you create the target table? Did you let the Write Table operator create the table? If so, it is possible that the expressor type integer was defined as an integer in the target table even though it needed to be a BigInt.
First, let's try to get the application to run.
- Place a Transform operator between the SQL Query operator and the Write Table.
- Open the rules editor and draw a mapping from the input RECID to the output RECID; this will create an expression rule.
- Hard code some value into the expression rule, for example: utility.sequence(). This will give each row a unique value.
- Now run the dataflow.
As a permanent fix:
- You could modify the target table so this column type is BigInt.
- Then create a new schema for the Write Table operator from the table itself.
Let me know if this works out.
The error message told us it was the Write Table operator.
The error message said ‘parameter 93’ by which it meant the 93rd parameter in the SQL statement it was trying to execute.
So, just count down through the schema to the 93rd attribute.
The messages are not that clear sometimes, but once you have seen a few, how to interpret them starts to make sense.
John Lifter PhD
Principal Customer Success Engineer
Direct: +1 617 658 5356
275 Grove Street
Newton MA 02466