# How has OceanBase Database changed your approach to MySQL sharding and large-table performance?

We moved from a MySQL sharding setup to OceanBase Database and saw big gains in scalability and maintenance efficiency, with strong performance on tables with tens of millions of rows and complex joins. MySQL compatibility meant no application changes, and built-in partitioning removed the need for manual table splitting. We also streamlined analytics by avoiding ETL-style aggregation across multiple MySQL instances, and the Console UI plus MySQL tool integrations (like Navicat) were smooth. If you’ve made a similar move, what improvements or tradeoffs did you see?

##### Post Metadata
- Posted at: about 2 months ago
- Author title: Solution Architect
- Net upvotes: 1



## Related Product
[OceanBase Database](https://www.g2.com/products/oceanbase-database/reviews)

## Related Category
[Key Value Databases](https://www.g2.com/categories/key-value-databases)

## 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: about 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: about 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: about 13 years ago
  - Comments: 4