My client has a Windows Server 2012 R2 box with SQL Server 2016. We use PDI 7. The loads are run from Windows scheduler. It happens quite often that PDI stops somewhere in a job for no apparent reason. The lot of the transformation shows nothing wrong, just that it ends with STOP instead of END. This causes the job to stop prematurely and not doing all the transformations. This is one of the main reasons why my client now abandons PDI and goes (back) to SSIS. Who else has this issue and knows what causes it? I think it's [$#&^$#^#&^$} that it's so unreliable.
↧