My gut reaction is that I can't see anything wrong with multiple jobs running the same executable with different command-line arguments (which I assume is the way you plan have this one big executable to be able to handle the various tasks of the small executables).
Looking for a solution to run single executable from multiple jobs in SQL server Agent
We have various different small executables scheduled as jobs under the SQL Server agent. It becomes challenging to manage these small executables. When there's a small change then we need to update all of them one by one and also sometimes there's code redundancy in some of the exes.
I'm thinking to merge all small executables into one single executable for manageability and to avoid code redundancies. However, I still like them to be set up as different jobs under the SQL Server agent but all jobs are referenced to the same single executables with a parameter as Task Name.
Is it the right approach to point multiple different jobs to a single executable?
The reason for having different jobs is that each job different schedule time to run.
Hi @bhupinder singh ,
We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
Sign in to comment