FAQ migrate a schema from Jobserver to Edge
1 Can I migrate a schema that was not registered via Jobserver to Edge?
No, only JDBC schemas registered via Jobserver can be migrated to Edge via the Migrate Schema to Edge workflow. Schemas created by uploading CSV or Excel files to Jobserver cannot be migrated via the Migrate Schema to Edge workflow.
2 Are samples removed for a migrated schema?
No, the samples created via Jobserver remain available. You can remove the sample data from Jobserver. For information, go to Remove sample data.
3 Will Technical Lineage still work correctly after migrating a schema?
Yes, Technical Lineage will keep working because it relies on the last part of the asset's full name.
The Database asset that was related to the Schema and the new Database asset created via Edge have the same last part in their full name, the actual name of the database in the data source.
Full name of old Database asset: My_System>customer.
Full name of new (Edge) Database asset: Snowflake Cloud>customer.
4 Why do I still see the Migrate Schema to Edge option in the Actions menu for a migrated schema?
The option remains available for migrated schemas but the migration process will not start.
Once all schemas have been migrated, you can deactivate or remove the workflow from your environment. This will remove the Migrate Schema to Edge option.
5 Can I migrate multiple schemas in one action?
Like any other workflow, you can start the Migrate Schema to Edge workflow for multiple assets at once. By default, this will create user tasks for each selected schema asset. We are working on best practice guidelines to reduce the number of manual steps required when running the workflow in bulk.
Once available, we will communicate this via the release notes.
6 How can I decommission Jobserver?
Once all data sources have been migrated, you can decommission Jobserver. For all details, go to the Support center.
Learn more
Migrating a schema from Jobserver to Edge
Migration to Edge overview