When a job is set to execute as a scheduled task, which package code does it use. What I mean is, does that job use the package code found in the packages in SQL Server MSDB folder or it uses the current state of the database structure as derived from the most recent package execution. My packages are not set to automatically update the MSDB folder files as and when amendments are made in BIDS. I normally manually import those packages to MSDB from the default ..\bin folder. I’ve always wondered what will happen if I do not manually import to the MSDB folder the most recently modified package. I nonetheless always execute the new package amendments in BIDS and yet not always immediately replace the old package in MSDB folder. Any recommendations or advice about the best practice in this regard will be welcome over and above to the answer to my question. Mpumelelo

The package in msdb is completely independent of the same package in your BIDS project, except that it shares the same package name and id. Absolutely none of the changes you make in the BIDS project will show in your MSDB package until you import the BIDS package into msdb.Russel Loski, MCITP Business Intelligence Developer and Database Developer 2008

If your job is executing the package deployed on sql server (ie from MSDB database) then any change in the package (through BIDS) will not be reflected in the packaged deployed on sql server unless it is re-deployed/imported. If your job is pointing towards the package on file system then the change made to the package (through BIDS) will be reflected during the execution of the job. Nitesh Rai- Please mark the post as answered if it answers your question

Thank you for that quick response. Whilst I understand what you mean, my predicament is on the scheduled task in relation to the explanation that I have given. When I make amendments on the package on BIDS and execute that package, will the new changes be carried to the scheduled task “knowledge” so that when that task runs it will use the most recent database structure as derived from the most recent package execution in BIDS regardless whether the package has been imported to MSDB or not? Please note that the amendments that I’m referring to here happen after the scheduled task has already been set in SQL Server Agent. Mpumelelo

How are you pointing towards the .dtsx file in the job/scheduled task?Nitesh Rai- Please mark the post as answered if it answers your question

I'm pointing towards the packages in the MSDB. I think your responses answer my question. It’s only that I got confused by something relating to Analysis Services Processing Task in the BIDS Control Flow. If I remember well, there is somewhere where it was inferred that when the Analysis Services automated task runs, it maintains the existing structure in the database, not on BIDS. Correct me if I’m wrong, but I think that is what I deduced. It’s about two weeks now since I read that and I can’t even remember where I got it from. All the same, I understand what you have said about the SSIS scheduled tasks vis-à-vis packages (MSDB or File system). It means that I will have to update my MSDB packages as and when I make changes in BIDS given that my scheduled tasks are pointing towards MSDB. Mpumelelo