Help Center/ Data Replication Service/ User Guide (ME-Abu Dhabi Region)/ FAQs/ Product Consulting/ How Do I Solve the Table Bloat Issue?

Updated on 2023-02-02 GMT+08:00

View PDF

How Do I Solve the Table Bloat Issue?

In the full migration phase, DRS uses the row-level parallel migration mode to ensure migration performance and transmission stability. If the source database data is compact, table bloat may occur after data is migrated to the RDS MySQL database. As a result, the disk space required is much greater than that of the source database. In this case, you can run the following command in the destination database to free up the space:

optimize table table_name

The OPTIMIZE TABLE command locks tables. Do not run this command when you operate table data. Otherwise, services may be affected.

Parent topic: Product Consulting

Previous topic: Does DRS Support Resumable Uploads?

Next topic: Why Cannot I Select RDS Read Replicas on the DRS Console?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.