balajij8
Esteemed Contributor II

The catalog table generally adds maintenance overhead in manual cases as it can drift out of sync with actual queries if managed manually. Databricks capabilities might be enough as you can use Workspace search (searches across query names and content including SQL comments), Folder browsing works fine up to 100-200 queries per folder, System tables automatically tracks who ran what and when and SQL comments contain all the metadata you need

You can start simple and add complexity only if needed. 

  1. Start with: Folders + naming convention + SQL comment metadata
  2. Use workspace search when you need to find something
  3. Query system tables periodically to identify unused queries & usage statistics
  4. Add a catalog table or an app that takes the request info & load the catalog table or you can run it via workflow when Workspace search isn't sufficient & you get complex reporting requests

You can skip additional table unless you're managing thousands of queries or need sophisticated reporting/analytics on the requests as the lightweight approach (folders + naming + comments) is usually sufficient for direct cases.

90-day rule is a trigger to highlight unused queries. You can archive it using workflows after a review.