Error handling

  • I have a DTS package that abuot halfway through once I BCP in about 10 files, I wanted to run a basic count(*) against some tables to make sure that the counts were great in the new tables as opposed to the old ones. If the new tables record counts are greater than goto next step else I want the entire packaged stopped. Any ideas?

  • This was removed by the editor as SPAM

  • HI Dude,

    You should have a loop dts to get each file at the time. After bcp the file you can get counts with a select statement and past this to a global variable. Next time you can compare you new count with a gv and validate if is greater goto different step using workflow else error and stop the pkg.

    Johnny

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply