Environments

The Environments section allows you to configure various environments for your project. You can add new environments, edit existing ones, or delete environments as needed.

Environment Types

You can configure the following types of environments in DATAMIMIC:

• Database:
• Kafka
• Mongo
• Data Warehouse

Tip

If a required environment type is missing, please get in touch with our team to enable this environment type for your account or instance.

Managing Environments

Once you have added environments, you can manage them from the Environments pane.

Manage Environments

Available Actions

• Add: Add a new environment.
• Scan Metadata: For database environments (except SQLite), scan the connection to create or refresh database metadata.
• Reset Metadata: Remove stored metadata for the selected database environment.
• Edit: Modify the settings of an existing environment.
• Delete: Remove an environment.

Danger

Deleting an environment is a permanent action and cannot be undone.

Scan Metadata (Database Only)

Use the Scan Metadata action (repeat icon) in the table row to create or refresh database metadata for the selected environment. This action is available only for database environments that are not SQLite and prompts for confirmation before starting.

Reset Metadata (Database Only)

Use Reset Metadata to clear stale or inconsistent metadata before running a fresh scan.

Recommended sequence after schema changes:

1. Reset Metadata
2. Scan Metadata

Adding an Environment

To add a new environment, click the Add button on the top right of the Environments pane.

Wizard Steps for Adding an Environment

The wizard guides you through several steps to configure your environment:

1. Choose Name And Type

Provide a name for your environment and select one of the environment types.

• Database
• Kafka
• Mongo
• Data Warehouse

Choose Environment Type

1. Database Settings

Configure your database settings. For example, if you select PostgreSQL, you will need to provide details like Host, Port, Database name, Schema, User, and Password.

Oracle-specific notes:

• Oracle connections support both service name and SID targets.
• If both service-style target and SID are provided, service-style resolution is preferred.
• Legacy Oracle setups that only provide database are still treated as service-name style target resolution.

Configure Database Settings

Test your Database Settings

1. Confirm

Review your settings and confirm the creation of the new environment.

Tip

You cannot find your database system? Get in touch with our team to enable this type for your account or instance.