Solution to phpmyadmin import (import) file restrictions

The last time I used phpmyadmin to back up mysql databases without segment size, I suddenly backed up more than one hundred MB of SQL data. when I imported the data, I was prompted to import the data more than 2 MB. some time ago, once, I used the automatic segmentation processing on the website background. this time I encountered this problem and decided to solve it. I searched the internet for solutions from our predecessors. most of them mentioned modifying php. upload_max_filesize in ini, but this problem is still prompted after modification; but when phpmyadmin prompts this problem, there is a line of English prompt in the lower right corner, which roughly means to solve this problem, you can refer to the phpmyadmin document. click this link and phpmyadmin will automatically find the following instructions:

[2, 1.16] I cannot upload big dump files (memory, http or timeout problems ).

Starting with version 2.7.0, the import engine has been re-written and these problems shocould not occur. If possible, upgrade your phpMyAdmin to the latest version to advantake tage of the new import features.

The first things to check (or ask your host provider to check) are the values of upload_max_filesize, memory_limit and post_max_size in the php. ini configuration file. all of these three settings limit the maximum size of data that can be submitted and handled by PHP. one user also said that post_max_size and memory_limit need to be larger than upload_max_filesize.

The above file roughly indicates that when a large file is imported, first check php. upload_max_filesize, memory_limit, and post_max_size in the following three parts of the ini configuration file. we recommend that you modify the value slightly greater than the imported large SQL database file. follow this prompt, I modified the above three in php. after the value in ini, the php environment is restarted. during the next import, although phpmyadmin still shows the maximum import limit: 20,480 KB, the huge 80 MB database file has been successfully imported.