Scott's advice is solid. I suggest you compare execution times between the solutions offered and then you'll see why.

Is this something which used to work and has started failing, or has it never worked?

What do you want to see if the values are different? Which value takes precedence?

--Deleted

• This reply was modified 1 years, 10 months ago by Phil Parkin.

SSIS can run compiled code through the use of an Execute Process task.

Thanks for the response..

how do we check what you recommended ?

https://www.sqlservercentral.com/blogs/quick-tip-wmi-alerts-and-sql-server-agent-permissions..

Let me check and get back...

But the query captures data from 100+servers...so how does this work...check on all servers...

Assuming the package is deployed to SSISDB, it is possible to execute it by calling a stored procedure.

Stored procedures can be called from a SQLCMD command line and parameters can...

The tool should allow both scheduling and manual execution of jobs.

I'd prefer an attractive interface where we configure jobs, set up who can execute those jobs and perform the execution...

Might be a bit to powerful for what you need but check out dSeries workload automation from Broadcom, used that in the past for this type of centralised job...

Thanks for responding. I'm hoping to find something a bit prettier than SQL Agent, and ideally a product which is independent of SQL Server, as it may be used for...

Note to self: remember to rent a Lambo one day.

I haven't had this, as far...

I first added an 'Expression task' to the Control flow but then nothing was passed to the Source Editor query window...I wonder why? What is it for then...

The Expression Task allows...

I've been having lots of days like that recently. Then again, I am working with Azure Data Factory.

I don't think you can control the format of Agent history messages. But maybe you could write any errors to a table and then query that.