Purpose:
The attached script is to be used to find any conflicting database tables and columns on your vBulletin 2 installations. Please note that this script will not alter your database in anyway, it will simply identify any problems that may exist.
You will need to rectify this before you can attempt the vBulletin 3 upgrade.
How to use this script:
Simply upload database_conflicts.php to your current vBulletin 2 installation in the root folder and then run the script in your browser by visiting http://www.mydomain.com/forums/database_conflicts.php
Any problems will be identified.
Note:
If the script reports that you have a column conflict, dont remove this right away as this may be used in any hacks or modifications that you currently have installed on your board. These columns will have to be dropped or renamed before you can upgrade to vBulletin 3.
If the script reports that you have a table conflict (ie: you have a table called foo and vBulletin 3 also wants to create a table called foo, you do not have to delete your foo table. All that you will need to do is temporarily rename your foo table to something like foo_temp while you run the vBulletin 3 installation / upgrade, and when you have finished, use the tools provided in vBulletin 3 to add a table prefix to your vBulletin tables. For example, you could use a table prefix of vb3_, which would make the vBulletin foo table become vb3_foo. You can then rename your existing foo_temp table back to foo and continue.
If you have any problems post here
The attached script is to be used to find any conflicting database tables and columns on your vBulletin 2 installations. Please note that this script will not alter your database in anyway, it will simply identify any problems that may exist.
You will need to rectify this before you can attempt the vBulletin 3 upgrade.
How to use this script:
Simply upload database_conflicts.php to your current vBulletin 2 installation in the root folder and then run the script in your browser by visiting http://www.mydomain.com/forums/database_conflicts.php
Any problems will be identified.
Note:
If the script reports that you have a column conflict, dont remove this right away as this may be used in any hacks or modifications that you currently have installed on your board. These columns will have to be dropped or renamed before you can upgrade to vBulletin 3.
If the script reports that you have a table conflict (ie: you have a table called foo and vBulletin 3 also wants to create a table called foo, you do not have to delete your foo table. All that you will need to do is temporarily rename your foo table to something like foo_temp while you run the vBulletin 3 installation / upgrade, and when you have finished, use the tools provided in vBulletin 3 to add a table prefix to your vBulletin tables. For example, you could use a table prefix of vb3_, which would make the vBulletin foo table become vb3_foo. You can then rename your existing foo_temp table back to foo and continue.
If you have any problems post here