Prerequisites

This page provides a checklist of requirements to help you to prepare for data generation jobs. Completing these steps ensures the Syntho application is correctly configured, accessible, and ready for data generation and management. Please follow each step to confirm your setup meets all prerequisites.

1. Deployment and Initial Setup

• Application Deployment: Ensure the application is deployed successfully, and the UI is accessible. Verify that the first admin user can log in, see Deployment Guide for more information.

• User Accounts and Access Management:

  • Ensure that admin and user accounts are set up.

  • Credentials (username/password) are distributed securely, adhering to internal policies of User Management Guide.

2. Database Access Configuration

• Source Database: Confirm that day-to-day users have read-only access to the source database. Write or other permissions should not be required.

• Destination Database: Ensure users have access to the destination database, including the ability to perform operations such as table truncation, which is necessary for multiple data generation runs.

3. Workspace Configuration

• Workspace Creation: Create a workspace following the Workspace Setup Guide.

• Database Connection Test: Verify that the source database is available and accessible within the Syntho application by performing a connection test:

  • In the Syntho application, navigate to Workspace Settings and select Database Connections.

  • Input the connection details for both source and destination databases and select Test Connection.

  • Ensure a successful connection is indicated by a green checkmark, confirming access to both databases.

4. Data Alignment and Preparation

• Data Types Alignment: Ensure data type consistency between source and destination databases. Data types should be appropriately set:

  • Date columns as Date

  • Integer columns as Integer

  • Decimal columns as Decimal/Float

• Schema Consistency: The destination database must have the same tables and columns as the source database but should remain empty, with write access enabled.

• Data Integrity: Given that the source database may change during a data generation run, referential integrity errors are likely to occur. To prevent this, it is recommended to create a dump of the production database prior to starting the de-identification process. This ensures consistency and reduces the risk of errors during the run.