Details
-
Feature
-
Status: Deferred (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Current Situation
- The JITL Job JobSchedulerPLSQLJobJSAdapterClass provides the execution of vendor-specific PLSQL scripts running with Oracle. This requires use of an Oracle JDBC Driver that supports vendor-specific SQL syntax. Therefore the job implementation does not use a hibernate database access layer.
- Vendor-specific syntax is not supported for any other database systems.
Desired Behavior
- Similar to the JITL Job JobSchedulerPLSQLJobJSAdapterClass for Oracle it should be possible to use Transact SQL syntax for Microsoft SQL Server.
- The new job will not make use of the hibernate database access layer.
- The job will support integrated security which means that no user and password have to be specified.
- The job will support use of a credential store with the following parameters:
- db_user = cs://some/path/entry@user?file=credentials.kdbx
- db_password = cs://some/path/entry@password?file=credentials.kdbx
- db_url = cs://some/path/entry@url?file=credentials.kdbx
- The job will support use of files with SQL scripts.
Example Script
-- * Process some data declare @myNumber int; set @myNumber = 90; -- Execute declare @threshold datetime; set @threshold = DATEADD(DAY, DATEDIFF(DAY, 0, GETDATE()), -@myNumber ); select @threshold; update myTable set oldField = null, newField = null where myField < @threshold;