Schemas

Schema settings

The Settings tab holds the technical conventions for one schema. These choices shape everything Kenseme generates from it: create and migration scripts, Pipeline load procedures, and AI naming suggestions.

In the app: Data Model › Schemas › your schema › Settings tab

[screenshot]
The Settings tab with Schema Settings, Schema Naming Settings and Environments visible.

Before you start

The dialect, naming and environment sections, and Delete Schema, need Read/Write access to the schema. Read Only users don’t see them.

Default dialect

Under Schema Settings, Default Database Dialect sets the SQL dialect for this schema’s views, scripts and other SQL objects.

  1. Pick a dialect from the drop-down.
  2. The change saves straight away. A message confirms Default dialect updated to ….

Warning: Changing the dialect doesn’t rewrite SQL you’ve already written. It changes what Kenseme generates and which dialect new SQL starts in. To get a converted copy of a whole schema, clone it to another dialect instead.

See Supported database targets and Dialect-specific output notes.

Naming conventions

Schema Naming Settings tells Kenseme how names should look. It guides AI naming suggestions (Suggest Names) and the names Kenseme generates for new objects.

Group Setting Example
Table Settings Table Name Casing Pascal Case, Camel Case or Snake Case
Table Prefix tbl_
Column Name Casing Same options as tables
Table Name Format Singular or Plural
ID Column Suffix _id or Id
Maximum Column Name Length A number, for targets with short identifier limits
View Settings View Casing, View Prefix vw_
Index Settings Index Casing, Index Prefix idx_
Stored Procedure Settings Stored Procedure Prefix sp_ or usp_

Click Save Settings when you’re done.

Tip: Settle conventions early. Renaming later is possible, but every rename after the fact is manual work.

Environments

Environments map this schema to a real database (or catalog) and schema name per environment, such as Dev, Test and Prod. When you generate scripts or procedures, you pick an environment and its names are substituted into qualified object names.

  1. In the Environments section, click Add Environment.
  2. Fill in:
    • Environment label (required), for example Dev.
    • Database / catalog (optional), for example OLTP_Prod.
    • Schema override (optional): the schema name in that environment, if it differs. Leave it blank to use the schema’s own default.
  3. Click Save.

Each row has Set Default to make it the default environment, plus edit and delete actions.

Note: Only names Kenseme qualifies are substituted. Names hard-coded inside view or procedure bodies are not rewritten.

Attribute groups

Attach attribute groups so objects in this schema can carry your custom metadata.

  1. In Attribute Groups, click Add Group.
  2. Pick an Attribute Group from your organization’s groups.
  3. Tick the Entity Types it applies to (tables, columns, views and so on).
  4. Click Add.

The grid shows each group’s Group Name, number of Attributes and Entity Types. Use the edit icon to change the entity types, or the remove icon to detach the group. See Custom attributes overview.

Delete the schema

The Danger Zone at the bottom of the tab has Delete Schema.

  1. Click Delete Schema and confirm.
  2. If Pipelines depend on the schema, Kenseme lists them and asks you to confirm the delete again.

Deleting removes the schema’s tables, columns, SQL objects and related data. The confirmation says they can be restored within 30 days.

Warning: Deleting a schema in Kenseme never touches your real databases. It only removes the design.