hope you arr alright and it would be amazing if you could help me as I am totally puzzled.
I have a job that used to run for about one minute.
I did not do any changes to that job at all and from one day to another the job takes about an hour to run and produces thousands of warning messages (all the exact same).
There have not been any updates or other changes prior to this warning message and I have no idea how to resolve this.
The Dataflow is rather simple with some joints in it, Source is a SQL table target is SQL table.
The Error message I get is:
|Data flow DF_FACT_OPEN_ORDERS_EIMEA_PRISM_SYSTEM_9|Transform Query_3-Join5
ODBC data source <SQL-APPLICATIONS-DBS\APPS1> warning message for operation <SQLFetchScroll(rowStsArray[])>: <[Microsoft][SQL Server Native Client 10.0]String data, right truncation
Yes I had that problem in one environment. In my case, it was a particular field in which we generate a 32-character GUID. The field was a VARCHAR2(32) field, there were no trailing spaces or special characters. I even substringed it to make sure it was only 32 characters. (You sort of get desperate after a while).
Turns out that if I removed the Table Comparison transform from the Data Flow , turning the Data Flow into a straight pipe into a target table (I enabled Auto Correct Load just for my testing) … the problem went away. Everything was fine. I put the Table Comparison transform back… and the problem returned. So somehow the output of the Table Comparison, even though this particular field was NOT part of the compare columns (!!) was somehow causing this behaviour.
In the end, I just extended the length of that particular column with a few characters and the problem went away. Even though ALL entries in that column are 32 characters long and there are no special characters or nothing.
I have no idea if this is remotely helpful, or not, but if your situation is somewhat the same, this may help you to work around the problem. I admit, it’s not an ideal solution and Í don’t know of an immediate cause or fix but in the end, I gave up on actually trying to debug this to the actual root cause and I just applied a bandage and moved on.
yes that could be the reason, I narrowed it down in which transform the issue was and then played a little bit with the field types and some casts and got rid of the warning. But am not entirely sure where it came from.
(BOB member since 2007-01-10)
(BOB member since 2007-09-12)