Can an SSIS Package be deployed at the SAME TIME as when its' SQL JOB is running the same SSIS Pkg?


I have SQL JOBS that run my SSIS Packages each night.

I have a FIX to one of my packages that needs to be deployed tonight and the normal SQL JOB that runs the normal package, runs at 7pm each night.

Question: Can the SSIS Package that contains a small FIX, be deployed AT THE SAME TIME as the normal SSIS Package is "running"?

We may NOT be able to "disable" the SQL JOB in time to prevent the 7pm running and so this is why I'm wondering.

SQL SERVER 2008 is our system.

LVL 17
MIKESoftware Solutions ConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rainer JeschorCommented:
where have you stored your SSIS packages? On the file system or in MSDB?
Jim HornMicrosoft SQL Server Data DudeCommented:
The only way this would be possible is if SQL Agent or whatever scheduling/execution tool you are using makes a 'virtual' copy of the .dtsx before it executes, which is highly unlikely, so my strong guess is 'No'.

Just out of curiosity, wouldn't it be better to fix, then test the package, then deploy to prod?

Even better, hotwire your SSIS package with a 'testing' variable so that the package can be executed in 'test mode' by passing 'TEST' into that variable into the command line that executes it.  Then the SSIS packages does whatever it does in prod, but writes files in a test folder / doesn't mark rows as processed / doesn't do anything that would interfere with a 'prod' run.

That way, turn the schedule (with 'PROD' passed as that variable, or even better NULL = PROD) fix, test by deploying to prod and executing with a passed 'TEST' parameter, then once you are satisfied it is working correctly turn the schedule back on (aka turn the prod runs back on).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vitor MontalvãoMSSQL Senior EngineerCommented:
CRXIuser2005, do you still need help with this question?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.