从一种数据库结构迁移到另一种数据库结构
我有一个定制网站，我想将其迁移到看起来更强大的商业解决方案。举个例子，假设该网站当前正在运行一个由学生使用 AZ 制作的论坛脚本，目标是将其传输到 vBulletin 等平台。通常建议采用哪种方法从一种数据库结构迁移到另一种数据库结构？在分析表（例如用户）之间的差异时应该注意什么？如何自动将数据从一个数据库转换到另一个数据库？
I have a custom-made site which I want to migrate to a commercial solution which appears more robust. For the sake of an example, let's say the site is currently running a forum script made from A-Z by a student and the objective is to transfer it to, say, vBulletin. What approach would be generally advised for migrating from one db structure to another? What should I look out for when analyzing differences between tables (users for example) and how could I go about automating the transformation of data from one db to another?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
取决于您的“学生”如何构建数据库，以及您如何生成 vbulletin 所需的任何元数据。论坛不仅仅是用户和帖子。通常还有大量其他数据根本不存在和/或采用完全不同的格式，而简单的“重命名此字段”或“更改该表”类型转换无法处理这些数据。
在两个数据库驱动应用程序之间移动时，可能需要大量的数据处理，并且如果源（或目标）的结构很差，则可能无法以脚本方式完成此操作，只能手动处理工作。
Depends on how your "student" structured the DB, as well as how you'd generate any metadata that vbulletin requires. A forum is not just users and posts. There's usually a ton of other data alongside that will simply not be present and/or in radically different formats that a simple "rename this field" or "change that table" type transformation cannot handle.
When moving between two database-drive apps, there's likely to be a significant amount of data massageing required, and if the source (or destination) is poorly structure, it may not be possible to do it script-wise and only a manual process will work.