Default catalog created wrong on my workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I am also able to see just these 3, I think it is meant to be "My organization"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@NandiniN My organization is a grouping not a catalog. When I run SHOW CATALOGS I get below, which tells me it could be probably "system", but that is not setup as default right now. The terraform documentation I link I provided above says we should have a catalog created by default matching workspace name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
The legacy Hive metastore is maintained for backward compatibility. When you start using Unity Catalog compatible compute i.e. when the workspace has an assigned Unity Catalog metastore, and the cluster is in access mode 'Shared' or 'Single User', or in SQL warehouses then you to reference a fully qualified 3 level name. Catalog.Schema.table.
Run the following SQL queries to check if Unity Catalog is enabled and to list the catalogs and schemas.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@saurabh18cs Ours is a new account and as I represented in the screenshots above, for new accounts databricks documents suggests we will have a new catalog created matching workspace name. However that never happened in our account and the default catalog for our workspace points to the hive_metastore catalog. I do not want to use hive_metastore catalog. I am working towards creating my own catalog for the workspace and attach it to the UN=nity metastore, but I expected a new catalog be already there as per their documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@amarnadh-gadde let me explain you again to make it more clear.
1) My orgaisation will act as your unity catalog catalog.
2) Ignore what is showing default there and ignore hive_metastore
3) start using unity catalog via uc enabled compute and 3 level namespace (catalog.schema.table)
Just try using it , I believe everything is correct at your side.

