Multi-Schema Creation FAQ¶

General¶

What is multi-schema source datastore creation?¶

It is a feature that allows you to discover and select multiple schemas from a single connection and create all corresponding source datastores in one step, instead of adding each schema individually.

Which connectors support multi-schema creation?¶

JDBC-based connectors with a schema field support multi-schema creation, as do the AWS Glue Native, Hive Native, and Unity Catalog Native connectors. DFS-based datastores (Amazon S3, Azure Datalake Storage, Google Cloud Storage) have no catalog/schema hierarchy, so they support bulk creation from several root paths instead, with the {{path}} or {{path_segment}} placeholders in the name template. See the full list in Supported Connectors.

Can I use multi-schema creation with an existing connection?¶

Yes. You can either create a new connection or reuse an existing one. When using an existing connection, you can only configure the datastore-specific properties (catalog, schemas, name template, teams, group, and initiate sync).

Is there a limit on how many schemas I can select at once?¶

There is no hard limit on the number of schemas you can select for creation. However, the validation endpoint accepts a maximum of 50 schemas per request. If you have more than 50 schemas, validate them in batches. The creation endpoint itself has no such limit.

Can I edit the datastores created in bulk after creation?¶

Yes. Each datastore created through the multi-schema flow is a regular source datastore. You can edit, delete, or reconfigure them individually through the Edit Datastore just like any other datastore.

Can I delete all datastores created in bulk at once?¶

No. There is no bulk delete option tied to the multi-schema creation. Each datastore must be deleted individually through the Delete Datastore settings.

Can I use multi-schema creation for enrichment datastores?¶

Yes, through the API. Set enrichment_only: true in the bulk creation request and every datastore in the batch is created as an enrichment datastore. This option is not available in the UI, only via the Datastore API.

A new schema was added to my database. How do I add it to Qualytics?¶

Run the multi-schema flow again using the same connection. The schema discovery will show all available schemas, including the new one. Schemas that already have a datastore will display a warning icon, so you can easily identify and select only the new schema.

Alternatively, you can use the Datastore API to discover and create the datastore for the new schema programmatically.

How do I know which datastores were created by multi-schema vs. individually?¶

There is no visual indicator that distinguishes them. Once created, a datastore from multi-schema is identical to one created individually. If you need to track this, use a consistent naming convention through the name template (e.g., batch_{{schema}}) or apply a specific tag during creation.

Permissions¶

Who can use multi-schema creation?¶

Users with the Manager or Admin role can use multi-schema creation. This is the same permission required to create a single datastore.

Are there different permissions for discovery, validation, and creation?¶

No. All operations in the multi-schema flow - catalog discovery, schema discovery, validation, and bulk creation - require the same Manager role.

Can I assign different teams to different schemas?¶

No. In the multi-schema flow, all source datastores created in the batch are assigned to the same teams. If you need different team assignments, you can change them individually after creation through the Edit Datastore settings.

Schema Discovery¶

How are schemas discovered?¶

When you provide connection credentials and select a catalog (if applicable), Qualytics queries the database's information schema to retrieve the list of available schemas. This happens in real-time during the creation flow.

What does the warning icon next to a schema mean?¶

The warning icon indicates that the schema already has one or more existing datastores in Qualytics. A tooltip shows which datastores are associated. You can still select it, but this will create a duplicate datastore for that schema.

Can I refresh the list of available schemas?¶

Yes. Click the refresh button next to the catalog or schema dropdown to re-query the connection and reload the available options.

Why are some schemas missing from the list?¶

The schema discovery relies on the permissions of the database user configured in the connection. If a schema does not appear, the user may not have the necessary privileges (e.g., USAGE on the schema) to see it. Verify your database user's permissions with your DBA.

Does discovery show system schemas (e.g., information_schema, pg_catalog)?¶

Yes - discovery returns all schemas visible to the database user, including system schemas. You can simply skip selecting them. Only the schemas you explicitly select will have datastores created.

Name Templates¶

What is a name template?¶

A name template is a naming pattern applied to every datastore in the batch. For schema-based connectors it uses the {{schema}} placeholder, replaced with each schema name: production_{{schema}} with schema public becomes production_public. For DFS connectors it uses {{path}} (the whole root path, with slashes turned into underscores) or {{path_segment}} (the last part of the path).

Is {{schema}} the only placeholder available?¶

For schema-based connectors, yes. DFS connectors use {{path}} or {{path_segment}} instead, since their datastores are created from root paths rather than schemas.

Can I use the name template without the {{schema}} placeholder?¶

Not for schema-based connectors: {{schema}} is required so that each datastore gets a unique name. For DFS connectors a placeholder is optional. Without one, the last segment of each root path is appended to the template, separated by an underscore, or by a hyphen when the template contains spaces.

Can I preview the generated names before creating?¶

Yes. A preview is displayed below the name template field showing how the first few datastores will be named based on your selected schemas.

What happens if the generated name conflicts with an existing datastore?¶

That datastore is not created. Qualytics rejects a generated name that already exists and reports it as an error ("Datastore '' already exists with id: "), while the other datastores in the batch are still created. Use a name template that produces names not already in use.

Can I rename a datastore after it was created by multi-schema?¶

Yes. You can rename any datastore through the Edit Datastore settings, regardless of how it was created.

Enrichment¶

Is linking an enrichment destination required?¶

No. The step is optional. You can click Finish after the datastore configuration to skip it. However, linking a destination is recommended for full data quality visibility.

Can I link different destinations to different schemas?¶

No. In the multi-schema flow, all datastores created in the batch are linked to the same destination. If you need different destinations for different schemas, change the link individually after creation through Link an Enrichment Destination.

Can I change the destination after creation?¶

Yes. Open the datastore's enrichment settings and pick another destination; there is no need to unlink first. See Link an Enrichment Destination.

What is the enrichment prefix?¶

The prefix is a string prepended to table names when Qualytics writes metadata to the enrichment destination. It helps uniquely identify which source datastore the enrichment data belongs to. It is generated from the name template and can be changed in the Enrichment Destination step.

Is the enrichment prefix the same for all datastores created in the batch?¶

No. Each datastore in the batch gets its own prefix, derived from its name, which comes from the name template and the schema name. You can change any of them with Edit prefixes in the Prefix section before you click Finish.

Integration with Other Features¶

Can I use multi-schema creation together with datastore grouping?¶

Yes. You can assign all newly created datastores to a datastore group during the creation flow by selecting a group in the form. All datastores in the batch will be assigned to the same group.

Can I add tags during multi-schema creation?¶

Yes, through the API. The bulk creation request accepts a tags field that applies the specified tags to all created datastores. The UI form does not currently include a tags field during creation, but you can add tags to individual datastores after creation.

Do the created datastores automatically appear in my team's view?¶

Yes. The datastores are assigned to the teams you select during creation and will be visible to all users in those teams according to their permission level.

Does multi-schema creation work with Secrets Management?¶

Yes. If your connection uses Secrets Management, you can use ${key} references in connection properties. The secrets are resolved dynamically each time the connection is used, including during schema discovery and datastore creation.

Operations¶

What happens when I enable "Initiate Sync"?¶

When enabled, a sync operation is automatically triggered on each newly created source datastore after creation. The sync operations run independently and detect containers and fields within each schema.

Do all sync operations run at the same time?¶

The sync operations are triggered sequentially as each datastore is created, but they run independently and may execute in parallel depending on system capacity.

Can I schedule operations in bulk for the datastores created?¶

There is no bulk scheduling option tied to multi-schema creation. Operations (sync, profile, scan) must be scheduled individually for each datastore. However, you can use the Datastore API to automate scheduling across multiple datastores programmatically.

Performance¶

Does multi-schema creation take longer with many schemas?¶

Yes. Each schema is validated and created individually within the bulk operation. More schemas means more validation and creation steps. For very large numbers of schemas (50+), consider breaking the operation into smaller batches.

Is there a validation limit?¶

Yes. The validation endpoint accepts a maximum of 50 schemas per request. If you need to validate more, split them into multiple validation requests. The creation endpoint itself has no such limit.

Can I run multi-schema creation while other operations are running?¶

Yes. Multi-schema creation does not block other operations. However, if you enable "Initiate Sync", the sync operations that start after creation will compete for system resources with any other running operations.

Errors and Troubleshooting¶

What happens if some schemas fail validation?¶

The validation runs per-schema and reports individual results. You can review which schemas failed, fix the underlying issues (e.g., permissions), and retry. Only schemas that pass validation will be created.

What happens if some schemas fail during creation?¶

The bulk creation operation is non-atomic - schemas that succeed are created, and schemas that fail are reported with error messages. You can retry the failed schemas individually or through a new multi-schema creation.

How do I retry only the schemas that failed?¶

Fix the problem the error describes and click Finish again. Only the schemas that failed are created; the others are not affected. On a new connection, the retry reuses the connection the first attempt saved, including when every schema was refused by the enrichment destination. The same holds when the first attempt created a new group with Create group, because the group is saved with the connection. Only when nothing saved the connection, with every schema failing before it was created (for example because its name is already taken) and no new group created, does Finish create the connection again. A schema already created keeps the name and prefix it was created with, so its prefix is locked in the Prefix section. If you switch to another connection, or select schemas in another database, the next Finish creates every selected schema, even one with the same name as a schema already created. Through the Datastore API, send only the failed schema names.

I don't see the catalog/schema dropdowns. Why?¶

Make sure you have:

1. Selected a JDBC or Native connector (DFS connectors show a Root Path multi-select instead).
2. Provided valid connection credentials.
3. Clicked Test Connection or waited for the catalog/schema discovery to complete.

If the connection credentials are invalid, the catalog and schema discovery will fail silently.

The schema list is empty even though my database has schemas. What should I do?¶

This usually indicates a permissions issue. Verify that:

1. The database user has USAGE or equivalent privileges on the schemas.
2. The catalog (database) was correctly selected (for two-step connectors).
3. The connection credentials are valid - try clicking the refresh button to retry discovery.

What happens to the datastores if the connection is deleted?¶

A connection can only be deleted if it has no datastores associated with it. If datastores still use the connection, the deletion will fail with a 409 Conflict error. You must delete or reassign those datastores first.