July 11, 2022 at 11:52 pm
Hello,
I need some advise on how to convert SQL agent jobs run a SSIS package( SQL agent job has source as "SSIS catalog" and has a SSIS package as destination which is under path example.. SSISDB - Catalog -->Project and where you select specific package)
Now, I want to change the SQL agent job source as "File System" and utilize the package. My understanding is that we have to make some changes to the existing package model and make a config file but I'm looking if you there are any best practices while changing this jobs source from SSIS to file system. I would really appreciate if any resource which has steps as well.
Thanks!
July 12, 2022 at 9:38 pm
Why would you want to do that? The catalog is a much better method of managing SSIS than using package deployment and a file system.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 13, 2022 at 9:52 pm
We have an issue when we apply new OS patches and for some reason SSIS catalog jobs fail.
I was researching on it as well. These are some initial steps..let me k now your thoughts.
Step 1 : Convert the SSIS package to Package deployment model
Step 2 : Enable package configuration and enable XML configurations
Step 3 : Tested and was able to convert to above model
Step 4: Copy the SSIS package local to the server
Step 5: Setup job and update connection string to specified environment.
July 16, 2022 at 4:01 pm
We have an issue when we apply new OS patches and for some reason SSIS catalog jobs fail.
I was researching on it as well. These are some initial steps..let me k now your thoughts.
Step 1 : Convert the SSIS package to Package deployment model Step 2 : Enable package configuration and enable XML configurations Step 3 : Tested and was able to convert to above model Step 4: Copy the SSIS package local to the server Step 5: Setup job and update connection string to specified environment.
I would not revert to package deployment and file deployment. There just isn't a good reason to do so - and stating that SSIS catalog jobs fail because you applied OS patches isn't a good enough reason. We patch our SSIS servers every month and catalog jobs just don't start failing because we patched them.
Without knowing anything more - my best guess would be that your source/destinations are in an AG and your connection settings are incorrect causing the jobs to fail because they are connecting to the wrong node. If that is the case, moving to package deployment isn't going to fix that problem.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply