Forum Discussion
bojanvelevski
3 years agoValued Contributor
The problem might be, and probably is, in the downstream snaps.
Try and isolate the snap to properly test and confirm if the problem is really in the SQL Server Execute.
gordon_ash
3 years agoNew Contributor
Hi [bojanvelevski],thanks, you are right, I disabled the snaps after the error pipeline (PE3) and the SQL Execute runs no problem; so there must be something wrong with the snaps further down the stream, I can investigate those.
Thanks very much.
- smudassir3 years agoEmployee
Thanks, I was not able to replicate the issue just with the SQL Server snaps in the pipeline. Can you share your pipeline here to atleast show the downstream snaps after the Sql Server snap?