schemachange VS bytebase

Our organization is transitioning from Microsoft SQL Server to Snowflake. We could use SQL Server Database Projects to deploy schema changes to our data warehouse within the SQL Server space. With Snowflake, the default tool is schemachange. Does anyone know of a database DevOps tool for Snowflake that is more like SQL Server Database Projects?

We use schemachange to deploy scripts, and we have a database prefix variable that we pass in to denote which set of clones this is, so you can spin up your own clone - so any scripts that work across databases have use that in jinja. We have a CICD pipeline in Jenkins (but I also have this replicated in a local Jupyter notebook) where we clone the DBs with this same prefix, apply the schemachange scripts from our stacks (we have multiple stacks and a deployment order through them to manage cross dependencies) and then you're good to go.

We have tried Terraform and others like Snowchange and in the end, we use Snowchange: - Terraform for Snowflake has a very tricky thing is that the table is replaced whenever Terraform detects a change. This is OK for AWS resources but it is bad for data thing like Snowflake - you don't want any change, unless you specifically want to. - We then have to use the second one, Snowchange. This one idea is simple: it marks the SQL files with versions, such as V0.1.1. Snowchange will only run the files if and only if the files are bigger than the biggest recorded in a table in Snowflake (which is done by itself). For example, if the largest version is V0.1.1, and some user accidentally changes the file of V0.1.0, since it is smaller than 0.1.1, the changes are not deployed. Users have to manually the file name to 0.1.2 for it to run.

Schemachange https://github.com/Snowflake-Labs/schemachange

I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:

For Snowflake, we ended up using this script: https://github.com/Snowflake-Labs/schemachange

We have been building https://github.com/bytebase/bytebase for 3+ years. You can think it of as GitHub/GitLab for SQL changes, with integrated GitOps, code review and deployment.

You can further check out this tutorial to get a feel of our GitOps solution

https://www.bytebase.com/docs/tutorials/database-change-mana...

We have been working on bytebase (https://github.com/bytebase/bytebase) for 3+ years to address this. With a change review workflow, environment propagations, and try not to disturb the dev flow if possible.

Migrations. All my database logic lives in version control.

Popular tooling like Phoenix, Hasura, etc have good built in migration stories.

https://www.bytebase.com looks really promising.

Hover, I do struggle with one big issue: changing database logic (views, functions, etc) that has other logic dependent on it. This seems like a solvable problem.

bytebase.com — Database CI/CD and DevOps. Free under 20 users and ten database instances

Bytebase offers a powerful GUI for schema migration deployments. This tutorial will show you how to use Bytebase to deploy schema migrations with features like SQL Review, custom approval, time scheduling, and more.

Now there are more subdivided practice: * Policy as Code: Sentinel, OPA * Database as Code: bytebase * AppConfiguration as Code: KusionStack, Acorn * ...... (Welcome to add more)

Bytebase is an open-source Database DevOps and CI/CD tool for teams, designed to centralize the control and secure your organization’s most valuable asset, the database data.

I use Bytebase to manage database changes for MySQL with GitOps workflow. I can manage my SQL scripts in my GitLab repo, and trigger a database change issue with committing a MR. Then Bytebase will record it after the issue is executed successfully. But I am not sure whether it supports procedures. Refer to https://github.com/bytebase/bytebase to get more details.