precedence constraint question

[rq]

In the DTS package I created, there exists a Transform Data task wherein a newly created SQL table is populated with data. Whenever this task is executed, results vary for this Transform Data task -- that means this newly created table could have several records at times or none at all. An Execute SQL task follows the Transform Data task. Is it possible to define a precedence contraint wherein the Transform Data task will execute ONLY if several new records where populated onto the newly created SQL table? I am aware of the Workflow property and how you can execute the succeeding task on success, failure or unconditionally.

 

[mrdenny]

Nope. What you can do it after the data is loaded check the table for data. If there is none, raise an error which will stop the package. If there is data do not raise the error and let the package continue.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[rq]

What task do you use to raise an error so that I can check the table for data?

 

[mrdenny]

This should do the trick.

if not exists (select * from table)
   raiserror ('There was no data in the table', 16, 1)

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)