# How are you handling review and approval for schema changes in Bytebase workflows?

What I like best about Bytebase is that review and approval are built into the change workflow: every DDL change goes through an Issue with SQL review, approval, then execution in one pipeline. It helps prevent the “oops, ran it straight on production” kind of accident, and it’s easy to add extra upstream checks like patch verification or ERD rule checks. The downside for us is pricing, since license cost scales badly as our DB footprint expands. How are others balancing governance benefits with Bytebase’s pricing as you grow?

##### Post Metadata
- Posted at: 7 days ago
- Author title: DBA
- Net upvotes: 1



## Related Product
[Bytebase](https://www.g2.com/products/bytebase/reviews)

## Related Category
[Database DevOps Software](https://www.g2.com/categories/database-devops-software)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4