Hi Todd!
I will give you the background:
This particular job will be used for archiving data.
Now, the user can decide whether the archival should take place in a year or
two or three and so on. So, a field in the database table will store this
value.
We need to fetch the last archival date, add the number of years and
calculate the next archival date.
I have implemented the scenario where the job is scheduled to execute every
day and the first task checks if it really needs to do the archiving "Today".
I was just wondering if we can somehow avoid sheduling the job to be
executed everyday. However, I guess it is a limitation.
Thanks again!
Regards,
B@ns
[quoted text, click to view] "Todd C" wrote:
> Hello B@ns:
>
> i think you are on the right track in your second scenario: Have the SSIS
> package itself decide, based on data in an external table, if it should
> procede with the main operation. Easy enough to do with the Control Flow
> aspect of SSIS.
>
> Just curious: once the package/job does run, what or who decides when it
> would be run again?
> --
> Todd C
>
> [If this response was helpful, please indicate by clicking the appropriate
> answer at the bottom]
>
>
> "B@ns" wrote:
>
> > Hi,
> >
> >
> >
> > We are trying to schedule a SSIS package as a job in the SQL Agent.
> >
> > However, we need to schedule the job dynamically.
> >
> > There is no fixed date (or period) when this job runs.
> >
> >
> >
> > Is it possible to dynamically schedule the job?
> >
> > The next execution date can be stored in a database table or a config file,
> > etc.
> >
> >
> >
> > If not, then perhaps we can include a task at the top of the Control Flow,
> > which, will check if the package needs to execute "today". For this the job
> > will have to be scheduled on a daily basis.
> >
> >
> >
> > Thanks in advance.
> >
> >
> >
> > B@ns
