I have a 3 data flows with an oledb source, a script component and a sql server destination that reports success and that it wrote the rows to the table in question. However, the rows are not written to the SQL Server 2005 table that is the destination. I have many other data flows in the same package that work exactly the same way that insert the rows they should insert in the destination table.
An example of the message I get indicating success is as follows:
[DTS.Pipeline] Information: "component "SQL Server Destination" (75)" wrote 289 rows.
Has anyone else seen this behavior or have an idea what might be wrong? Why would the data flow report success when the rows were not, in fact, inserted in the destination table?
I deleted the 3 data flows that were exhibiting the problem behaviour and re-created them from scratch. The problem went away after I did this. Don't know what the problem was but the three I deleted had worked previously.|||swells wrote:
I deleted the 3 data flows that were exhibiting the problem behaviour and re-created them from scratch. The problem went away after I did this. Don't know what the problem was but the three I deleted had worked previously.
Do you have an old copy of the package? It'd be interesting to compare and see what the differences were.
-Jamie
No comments:
Post a Comment