Implications of using waitfor delay task in ssis package on scheduled server -


i have question regarding implications of using waitfor delay in execute sql task on ssis package. here's what's going on: have source data tables due amount of data , linked server connection yada yada dropped , created every night. before package utilizes data runs have loop container. in container have execute sql task checks see source tables exist , if not, sends me , email via email task, goes execute sql task has waitfor delay of 30 mins (before looping , checking source tables again). thought pretty slick design others on team concerned because not know enough waitfor task. concerned package possibly interfere theirs, or slow down server, use resources etc....

from google searches didn't see seemed cause issues. can here speak implications of using task?

sql waitfor ideal requirement imo - i've been using in production ssis packages years no issues. can monitor via ssms activity monitor , see doesnt consume resources.


Comments

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

java - Cannot secure connection using TLS -