You can now easily increase the number of partitions in your SingleStore database, which is critical for scalability. This is achieved through a clever strategy that adds partition splitting to the work of a backup operation. The process involves taking a split backup, dropping the original database, and restoring the split backup. The restored split database will have new partitions with data from half of the original partition. To use this feature, you can run a command to take a split backup, drop the database, and then restore it. You should also pause your workload before taking the backup, add leaves if necessary, and consider unpauseing your workload after restore. Additionally, rebalancing partitions may be recommended, especially if you backed up to the local filesystem. The background columnstore merger will eventually compact the columnstore blobs, reducing disk space usage.