Import a schema
Schema import as a background job
A script import runs in the background, not in your browser. You can start a long import and walk away without losing anything.
In the app: Settings › Organization Settings › Schema Imports tab
Where to follow it¶
- Schema Imports tab. Organization Settings ›
Schema Importslists every import with its status and progress. Open one for the full import detail page. Organization Settings is for organization admins. - The schema itself. Tables, views and other objects appear on the schema’s tabs as each stage completes.
- Activity. Imports appear on the Activity page with other recent changes.
Script imports have their own tab; they don’t appear on the Background Jobs tab. The follow-on work they trigger, such as SQL object analysis, does. See Where to watch background jobs.
Closing the browser is safe¶
- The import runs on the server. Closing the tab or the browser doesn’t stop it.
- Come back later and it’s either further along or finished.
- Failures are listed on the detail page exactly as if you had stayed.
How long it takes¶
Most imports finish in seconds to a few minutes, depending on size. Splitting the script is quick; the tables and SQL objects stages take the most time on large scripts.
What runs alongside¶
- SQL object analysis. Each view, procedure and function the import creates is queued for analysis, which fills in its outputs, parameters and dependencies. Analysis shows on the
Background Jobstab. See AI in SQL object analysis. - Star schema checks. If the schema has star-schema plans, Kenseme checks whether the import changed anything they depend on.
Stop or restart¶
Cancelon the detail page, or the cancel icon on the Schema Imports list, stops the import. Objects already created stay.Resume Import(after a cancel) orResume All Failed(after errors) re-queues the pending and failed items.
If the import stops in Failed status, the message on the detail page says why. Fix the cause and resume, or start a new import.