For Enterprise customers, we guarantee 100% implementation success in 90 days. Contact us to discuss your specific requirements.
The ultimate goal is to make Bytebase the only tool to manage all human-to-db operations. It’s fine if your team has existing tooling and process. Bytebase can be adopted in phases to improve the database operational practices gradually:
1

Standardize ad-hoc change process (2 weeks)

2

Centralize data query access (2 weeks)

3

Integrate SQL review into CI (1 week)

4

Manage schema migration (4 ~ 8 weeks)

​
Phase 1 - Standardize ad-hoc change process

Duration2 weeks
Goals1. Remove direct human write access to database.
2. Streamlined change process with review, check, rollout, rollback, notification, and history.
Manage one-off DML changes (e.g. INSERT/UPDATE/DELETE) and out-of-band schema changes (e.g. add an index on emergency). Related features:

​
Phase 2 - Centralize data query access

Duration2 weeks
Goals1. Remove direct human read access to database.
2. Access grants are reviewed and recorded.
3. Dynamic masking policy depending on the querier.
Bytebase provides a web-based SQL Editor. Related features:

​
Phase 3 - Integrate SQL review into CI

Duration1 week
Goals1. Auto check SQL anti-patterns during CI.
2. Non-intrusive to the existing CI pipeline.
If your team has the existing database schema migration process in place. You can start by including the SQL Review check into the CI. Related features:

​
Phase 4 - Manage schema migration

Duration4 ~ 8 weeks
Goals1. Decouple schema migration from code release.
2. Streamlined change process with review, check, rollout, rollback, notification, and history.
You have achieved decent success in implementing Bytebase for your org. You may not need phase 4 if the application is OK to deploy schema migration together with the code release. On the other hand, it’s beneficial to use Bytebase for schema migration if you have any of the following situations:
  • Multiple servers connecting to the same database.
  • Multi-region database deployment.
  • Multi-tenant service and each tenant has its own database.
  • Long-running schema migration.
The implementation duration depends on how many existing schema migration workflows need to be moved to Bytebase. Related features (in addition to Phase 1):