Basic Structures

Repository Database

datasqill uses a repository database that is used by both the GUI and the datasqill Server. With the exception of runtime data, all other data is stored in versioned form, so that the state of the repository at any point in time can always be traced. The repository stores configuration data, transformations, scheduled runs, and runtime information.

Environments

datasqill can be used for multiple environments. Each environment has its own datasqill Server and associated repository database. Per production (datasqill license), there is a development environment that authorizes users to create new transformations, worksheets, or transformation directories. Environments that depend on this development receive transformations through deployments. The datasqill GUI connects to a master environment in which all other environments are registered.

Permissions

datasqill users are recorded. Individual permissions can be assigned to specific permission roles. Per environment, permission roles or individual permissions can be assigned to users.

Connections / Databases

In the datasqill GUI, all used connections to external databases, systems, web services, etc. are captured without being assigned to physical services. In transformations, these symbolic connections are used, and these transformations are deployed to subsequent environments in this way. On the target systems (datasqill servers), these connections are assigned to the credentials for the physical systems via a file. This allows connections to be set up to different systems in different environments.

Triggers

datasqill enables freely definable triggers for certain functionalities. These are used to trigger specific activities in the database at certain points in time (e.g. after establishing a connection, after writing, etc.) or to enable non-standardized functionalities (e.g. Truncate Table).