ALL CATALOGS in SHOW SCHEMAS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ06-03-2025 09:39 PM
Hi there,
I was checking though the Databricks Runtime 17.0 features while testing:
I faced below issues, is that anticipated or an issue which needs to be fixed?
This is how it was before Runtime 17.0 ๐
๐ I was expecting bronze and other schema starting with bron.
๐ I was expecting |schema | catalog name|, 2 column in the output.
๐ Also above 2 commands are running into error.
---------------------------------------------------------------------------------------------------------------------------------------
According to the release note
The SHOW SCHEMAS syntax is updated to accept the following syntax:
SHOW SCHEMAS [ { FROM | IN } { catalog_name | ALL CATALOGS } ] [ [ LIKE ] pattern ]
โ๏ธ Please let me know in case I am doing something wrong with the syntax or understanding.
Thanks!
- Labels:
-
Unity Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ06-04-2025 06:00 AM
I was able to reproduce same issue, I am working with the team, as this DBR is in Beta version we might see some changes on the behavior, so I will confirm if anything has changed around this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ05-29-2026 06:35 AM
HI @creativeIndex,
I stumbled upon this while looking for something else. I appreciate it's been a while, but I realise you haven't received a solution yet. Is this still an issue?
I just wanted to point out that you should use an asterisk (*) instead of a percentage sign (%) in your initial query. The command `SHOW SCHEMAS ... LIKE` does not use SQL wildcards like %. Instead, it expects a regex-style pattern where * acts as the multi-character wildcard. Therefore, a query like 'bro%' is treated literally, leading to no matches. Please try the following suggestion, and it should work.
SHOW SCHEMAS LIKE 'bro*';
In terms of your second question, I see it is working now. Please let me know if you encounter any issues.
If this answer resolves your question, could you mark it as โAccept as Solutionโ? That helps other users quickly find the correct fix.
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***