Add Create Catalog
Specifies if the table create scripts should include the CREATE CATALOG IF NOT EXISTS statement.
When enabled (the default), the generated deploy notebook for each target database starts by creating the target: on a Unity Catalog target it issues CREATE CATALOG IF NOT EXISTS ... MANAGED LOCATION ... using the catalog name and location passed to the notebook, and on a workspace without Unity Catalog it issues CREATE DATABASE IF NOT EXISTS instead. On Unity Catalog targets the same deploy notebook also creates the Temp Table Schema when one is configured.
When to Change This Setting
Keep the default Y so a deployment can bootstrap an empty workspace end to end. Disable it when catalogs are provisioned outside BimlFlex, for example when the deploying principal is not permitted to create catalogs in the workspace.
Related Settings
| Setting | Interaction |
|---|---|
| Use Unity Catalog | Determines whether a catalog or a database is created |
| Temp Table Schema | Also created by the deploy notebook when set |
Notes
- This setting is part of the Databricks settings category.
- The default value for this setting is
Y.