Query execution occurs in separate worker tasks so QiD remains responsive, even while executing multiple heavy tasks. Hence, one instance of QiD can be used to simultaneously perform multiple queries while continuing to analyse results and modify code as required.

QiD also provides a light client-side scheduling capability. You can set queries to run at specified times. This is driven by QiD on your PC so is not a full-blown server-side scheduler (although this is planned for a future release).

Execution History

Full details are provided on each statement and the steps and jobs in which they are executed. Error codes and messages are displayed. Execution start and end times are recorded, along with the number of rows returned or affected by each statement.

Execution History can be automatically cleaned up with full control over length of retention period, based on whether or not the queries were successful. The full text of queries is available within the execution history.

Error Handling

QiD, by default, understands and deals with different error levels independently of the particular DBMS. In addition, you can alter the default behaviour through settings and also through the script language.

A handy feature in QiD is the option to downgrade an error to a warning if the target of a DROP table, view or macro statement does not exist. This avoids the common problem (in some DBMSs) of scripts failing simply because tables don’t exist when the initialisation DROP / CREATE is performed.