• Phil Parkin - Thursday, May 3, 2018 12:45 PM

    skaggs.andrew - Thursday, May 3, 2018 11:32 AM

    Phil Parkin - Thursday, May 3, 2018 11:25 AM

    skaggs.andrew - Thursday, May 3, 2018 11:14 AM

    The package says the execution completed.  It acts as though the data flow completed without error.  However, when I look at links between the sources and targets within the data flow task, I can see that they have not all completed.  It's as if everything stopped and didn't complete the data transfer from source to target

    Sure, but that's not quite what I meant 🙂
    Is this just a simple data flow from A to B, or is there more complexity than that (eg, lookups, aggregations, joins)?

    Sorry.  This is a very straight forward source to target, no transformations involved.  I have a data flow task and inside I have probably 10 source to target paths setup.  This has been working for years and now that I have migrated the package, I am getting this error.

    No problem.

    Was this a straight migration, or were any changes made to the packages? Specifically, values like Rows Per Batch and Maximum Insert Commit Size on the data flow destinations?

    Is the RAM on the 2017 machine the same, or larger, than what you have on the 2008 instance?

    I essentially just copied the packages over from the old environment.  Maybe 10 packages in total.  I have already tested about 6 of them and no issues until now.  I did not make any changes to the package other than configure the connection manager.  I have the same amount of RAM on both machines.