FAQ

FAQ: schema importing

Looking for step-by-step instructions? Start with What schema import does.

What’s the difference between a script import and a connection import?

A script import reads a file or pasted text and creates objects in the background. A connection import reads a live database through a saved connection and shows you every proposed change to review before anything is written. See Import objects from a database connection.

What file types can I import?

.sql, .yaml, .yml, .json and .txt, or pasted text. See Supported import file formats.

How big can the script be?

Up to 5 MB, uploaded or pasted.

How long does an import take?

Seconds for a small script, several minutes for a large one. The tables and SQL objects stages take the longest. It runs in the background, so you can close the browser and come back.

Do I have to clean up my DDL first?

No. SSMS headers, GO separators, SET statements, comments and surrounding prose are all fine.

What happens to objects that already exist in the schema?

A script import skips them and never overwrites them; they show as Skipped. A connection import proposes updates for objects that differ, and you choose which to apply. Neither kind of import deletes anything.

Can I import into a schema that already has tables?

Yes. That’s the point of skipping existing objects: you can import a second script, or re-import a fixed version of the same one, safely.

Does a script import write descriptions?

Only the ones in the script, such as sp_addextendedproperty or COMMENT ON statements. Objects without one are left blank. Use Generate Descriptions afterwards for AI-written ones.

Do CHECK constraints become enums?

Value-list constraints, such as Status IN ('New','Open','Closed'), become enums in both kinds of import. Other constraints stay as they are.

Will Kenseme connect to my database during a script import?

No. A script import only reads what you upload or paste. Only a connection import talks to a database, and then only to read its catalog.

Where do I watch progress?

Organization Settings › Schema Imports, then open the import. Organization Settings is for organization admins. See Watch import progress.

What if some items fail?

Open the import, click Fix on each failed item to read the explanation and edit its DDL, then Retry with Changes. See Fix failed import items.

Many objects failed. What now?

If they share a cause, fix the source file and import it again into the same schema; existing objects are skipped. With more than 15 failures the import page offers Download Failed DDL.

Can I cancel an import?

Yes. Cancel on the import page stops it. Objects already created stay, and Resume Import picks up the rest later.

Can I import several files at once?

No. Run one import per file, one after another.