Import a schema

Fix failed import items

When part of a script import fails, the rest carries on. Each failed object stays on the import’s detail page, where you can fix its DDL and retry it on its own.

In the app: Settings › Organization Settings › Schema Imports › an import › Fix

[screenshot]
The Fix & Retry dialog: the "What went wrong" explanation above the editable DDL.

Before you start

  • You need to reach the import detail page, which is under Organization Settings (organization admins only). See Watch import progress.
  • Retrying writes to the schema, so it isn’t available while the organization is in read-only mode.

Open the dialog

  1. On the import detail page, find the failed item in Failed Items or in the All Items grid.
  2. Click Fix. The Fix & Retry: <name> (<type>) dialog opens.

Fix appears on Failed and Skipped items when 15 or fewer items failed in total. With more failures, fix the source file and re-import instead.

If Fix is disabled, an object this item depends on also failed. Hover the button to see which one (Fix … first) and fix that first.

What the dialog shows

  • What went wrong: a plain-English explanation of the failure, written by AI from the raw error. It shows Analyzing error... while it’s being written.
  • Show technical error: expands the raw error message.
  • DDL (editable): the object’s original DDL, which you can change. Reset to Original appears once you’ve edited it.
  • Retry count: how many times this item has been retried, once it’s more than zero.

Fix and retry

  1. Read the explanation. Common causes are syntax Kenseme didn’t recognize, an unsupported data type, or a reference to an object that doesn’t exist.
  2. Edit the DDL.
  3. Click Retry with Changes. Or click Retry Without Changes to try the original again, which helps when the failure was temporary.
  4. While it runs, the dialog shows what it’s doing, for example Parsing DDL and creating table....
  5. On success, the dialog closes and you see <name> imported successfully!

If other failed items depend on the one you fixed, Kenseme lists them and offers Retry All Dependents to retry them without changes. Choose Skip to handle them yourself.

Tip: Quick fixes that often work: swap a vendor-specific type for a portable one, remove partition or filegroup clauses, and quote a reserved word used as a column name.

When to stop fixing items one by one

  • Many items share one cause. Fix the source file and import it again. Objects that already imported are skipped, so re-importing into the same schema is safe.
  • You don’t need the object. A legacy view or a tooling artifact can stay failed. The rest of the schema works without it.
  • The construct can’t be expressed in the schema’s dialect. Leave it failed, or recreate a simpler version by hand.

A failed item stays on the import page as a record of what didn’t come across.