Configuration

A prerequisite for working with datasqill is the installation of the server components on a central server, as well as the installation of the datasqill Workbench on a client computer. In addition, connections, system parameters and other necessary configurations must be set up to enable working with datasqill. This is described in the course of this chapter. To do this, adjustments to the entries in the corresponding tables in the schema of the datasqill system user must be made.

Mailing Lists

In datasqill, datasqill@unknown-domain.com is the default email sender, but you can also store your own:

INSERT INTO vv_sqts_config (config_key1, config_key2, config_key3, config_key4, config_value, config_sort, config_comment)
                    VALUES ('SCHEDULER', 'MAIL', 'SENDER', '-', 'admin@datasqill.com', NULL, 'Email address of default email sender');

If you don't do this, this default email is used: datasqill@unknown-domain.com

For sending notifications by the datasqill scheduler, it is necessary to create mailing lists in the vv_sqts_mailing_list table accordingly. Multiple email addresses can be stored per mailing list. Use this INSERT statement:

INSERT INTO vv_sqts_mailing_list (mailing_list, mail) VALUES ('Operations','worker1@datasqill.de');
INSERT INTO vv_sqts_mailing_list (mailing_list, mail) VALUES ('Operations','worker2@datasqill.de');
INSERT INTO vv_sqts_mailing_list (mailing_list, mail) VALUES ('DWH-All','dwh-developers@datasqill.de');
COMMIT;

After that, you can use these lists in every batch, for example:

Proxy Packages

As a prerequisite for proper use, it is recommended to install proxy database procedures for Grant and Truncate functionality in database schemas with transformation-relevant objects (sources, targets). These must be granted execution rights for the datasqill system user.

The Grant proxy is used by datasqill to automatically grant the required access rights for data objects used in transformations.

The Truncate proxy is used to execute the commonly used Truncate functionality in schemas involved in transformations.

Versioning

The persistent components of datasqill are stored in tables that work with datasqill versioning. This ensures that old states of the persistent datasqill data can both be reported and restored.