好的，这就是情况，我有一个数据库，我从Localhost导出了大约30个或更多表，但是当我在实时网站上导入它们时，只有10个表，最糟糕的是，最糟糕的是用户表不掉't削减，这样我就无法登录仪表板并继续工作，所以我想知道我想念什么？？？我遵循了本教程的步骤，互联网上的许多教程引用或共享。
但是我有这种情况，什么都没有，为什么会发生这种情况，我该怎么办？？？
这是当地主机上的DB
，这就是导入的。
Ok so this is the situation, i have a database that i exported from localhost, there are like 30 or more tables, but when i import them on my live site, there are only 10 tables and worst of all is that the user tables didn't make the cut so i cannot login into the dashboard and continue working, so i wonder what am i missing??? I've followed the steps of this tutorial, which is quoted or shared by so many tutorials on the internet.
https://wordpress.org/support/article/backing-up-your-database/
But i have this situation, nothing goes as it should be, why is this happening and what can i do???
here is the db on the localhost
and this is what got imported.
发布评论
评论（3）
在导入屏幕上，在
部分导入下有一个复选框说明允许导入中断，以防脚本检测到其接近PHP超时限制。，请确保您没有选中该复选框。On the import screen, There is a checkbox under
Partial ImportstatingAllow the interruption of an import in case the script detects it is close to the PHP timeout limit., make sure you have that checkbox unchecked.您是否尝试通过SSH进入DB？如果可以这样做，则可以使用
源路径/to/import.sql导入。Have you tried getting into the DB via SSH? If you can do that, you can import using
source path/to/import.sql.因此，我得到了解决问题的方法，问题是我以GZIP格式导入DB压缩，而我需要做的是未经压缩的导入，与教程相反，该教程暗示使用压缩方法。即使是其他压缩格式也无济于事，因此如果没有压缩方法，导入工作也可以。我得到了所有的表格和所有应该导入的数据，以及本教程试图获得的。毕竟，DB太小了，例如10MB，因此没有问题，但是如果您的情况大于1GB或太大，那么也许此解决方案对您来说不是正确的。感谢所有帮助的人，他们确实对我的问题有所了解。
So i got the solution to my problem, the thing is that I was importing the db compressed in gzip format, and what i needed to do was import without compression, opposite to the tutorial which suggested the use of a compression method. Even the other compression format didn't help either, so importing without a compression method did the job. I got all the tables and all the data imported as it should be and as the tutorial was trying to get. After all, the db was just too small, like 10mb so it has no problem but if your case the db is bigger than 1GB or too big, then maybe this solution is not the correct for you. Thanks to everyone who helped, they indeed share some light about my problem.