- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2025 09:59 PM
Hi all,
I am working to resolve how to build tables in a development workspace catalog and then easily migrate the code to a production catalog without manually altering the schema name. For those unaware, you can't have the same catalog names in development as in productions. The catalog names are not unique to the workspace, but the catalog.
Maybe I am misunderstanding something about how this is to be approached, so happy to be guided, I haven't as yet found the document with that guidance. I might look for a cluster or Serverless warehouse tag to know what environment the catalog I am using to run against.
I could go to an external tool like Liquibase, but I wish to avoid that if I can. I am happy to manually run scrittps for deplyments, but don't want to have to go through and update code everytime I test or build now deployments
This feels like a glaring deficiency in the documentation and/or tooling