Recently, an IT Consulting Service asked Flux about how the Flux job scheduler interacts with a database. The main question that was asked was: can Flux schedule database jobs by using TSQL or Stored Procedures for databases such as SQL Server, IBM DB2, and Oracle? And also, what type of database level details can Flux track?
To answer the first question: yes, you can schedule database jobs that contain TSQL or Stored Procedures for SQL Server, DB2, and Oracle, by using Flux Database Actions and Stored Procedure Actions to execute SQL and Stored Procedures.
You could also call SQL Server through its command line by using a Flux Process Action. The same could be done with DB2 or Oracle. The Stored Procedures or TSQL can invoke the command line of Flux to submit jobs to a Flux engine.
For the second part of the question, Flux’s Audit Trail and Run History track the start time, stop time, and duration of every action in a Flux workflow, including Process Actions and Database Actions.
Lower level database information such as how many records were loaded, how many were rejected, or why is a database job running slowly, are not directly provided by Flux. Those pieces of lower level database info can generally be accessed through specific database utilities, Windows performance counters, and Windows specific scripts, which themselves can be wrapped inside of a Flux workflow in order to extract the desired information.