Table and Field Comparison Utility: Compare your database to out-of-the-box vBulletin
 

What is it?

This utility makes a comparison between the tables and fields in your database and the out-of-the-box vBulletin tables and fields.

It reports the following differences:

• The out-of-the-box vBulletin tables that are not in the database
• The database tables that are not a part of out-of-the-box vBulletin
• The out-of-the-box vBulletin fields that are not in the vBulletin tables
• The fields that are in the vBulletin tables but not a part of out-of-the-box vBulletin

New Features

• Ability to delete extraneous tables and fields from the compareutility.php file
  • Don't screw up your vBulletin database!

Installation

1. FTP the compareutility.php file into your /admincp directory in ASCII mode.
2. Go to the following page with your browser: http://www.YOUR-DOMAIN.com/YOUR-FORUM-DIR/YOUR-ADMINCP-DIR/compareutility.php
3. You need to set the following to yes to access the compareutility.php file:
   • ACP -> Usergroups -> Administrator Permissions -> Edit Permissions -> Can Run Maintenance Tools
4. To add a link to compareutility.php under the ACP -> Maintenance sidebar see this post.

UN-installation

1. Delete the compareutility.php file from your server.
2. Delete the cpnav_compare_db.xml from your server (from this post).

vBulletin version?

• Only tested on vBulletin 4.0.0 PL1 and 4.0.1
• May not work correctly on vBulletin 4.0.2
• May work on vBulletin 3.5 and up
• Won't work on less than vBulletin 3.5
• The vB3 version is located here

Screenshot

• None, run the script to see the report.

one of these days I should run this to help me clean up my database. I'm just a little worried that I will screw something major up or remove a field that is required by a hack.

Great Idea. Sometimes you remove a hack and always leave behide something on database. It's good to keep it clean.

Thank you

Edit: This should be default on vB just like the check files on maitenance menu.

Isn't this part of the diagnostics feature? That feature does pretty much everything you posted here.

Actually, no. This isn't part of the default diagnostics in vBulletin. Personally, I wish it was as it would make my job easier but until then this works well enough.

I'm going to be using this when I upgrade to 4.x. I never used your 3.8.x one but I'll be using this one! Thanks.

Nice work. Tagging for future use for now then then into install.

Would love to use this hack, as we have installed so many mods the last years. And i am sure it needs some cleaning.
But like Hornstar i am too frightened to mess something up badly :)

It looks like there a genius coder that used a ' in his table names. it doesn't appear that your script likes those.

i install it but ant things not show in admincp for reviwe this hack going to ..adress

This is exactly what I was looking for. Thank you! :)

Interesting tool!

But I wish the [Ask for Query] was working though...

I have a few out-of-the-box vBulletin fields that are not in my vBulletin tables:
holiday: varname
subscription: varname
userfield: field1
usergroup: albumpicmaxsize

...but now I have no idea how important these are, how come they are not there, and if/how I should be fixing the problem... :erm:

This util helped me a lot after an upgrade from 2.2.6 to 4.0.2 PL4. I had a lot of left over profile fields in my user table that were interfering with the postbit building functions. For instance, I had a "message" profile field on my 2.2.6 board and when I upgraded to 4.0.2, those fields were moved to the new profile structure. But, the old columns weren't deleted from the DB. What happened was the postbit message context was being merged with the user context. Both had a [message] key and since the user->message key was blank, my PM messages were showing up blank.

Very nice thanks

Has anyone used this on 4.03?

Update: Tested on my test forum and all worked well. THanks

Besides the permissions that one needs to set for the Admin, one needs to make the following change also.

In vb version 4.0.3 it is showing blog_attachmentlegacy under "The database tables that are not a part of out-of-the-box vBulletin", on the suite. I have not added this table.

Good job, Calorie. This is great! ;)

Same issue
did you find a fix ?
I posted over at vb.com as well
On test upgrade DB and the live forum
holiday: varname
subscription: varname
usergroup: albumpicmaxsize

Any idea when this mod going to officially released for vb 4.0.3 PL1?

It already works for 4.0.3 PL1. There is only one entry missing (in my above post) but other than that, it works fine.

Hello,
I have analyzed my database with this tool. I have these "The out-of-the-box vBulletin fields that are not in the vBulletin tables"

Can you help me to put them back? (I have a table prefix "mst_")
http://img14.imageshack.us/img14/3868/capturecq.jpg

What do you mean "put them back"? They are already there.

Isn't they are the fields which are supposed to be in the tables?
I mean, my mst_groupmessage table doesn't have any field called discussionid
mst_pmtext table doesn't have any field called reportthreadid
mst_profilefieldcategory table doesn't have any field called allowprivacy
mst_usergroup table doesn't have any field called albumpicmaxsize.

So, is there any way, by queries, I can put those fields back in the tables?

Those are fields, not tables in that pic you posted. They wouldn't be there unless the table that holds them was there also. You are fine.

The tables are there.. not the fields/columns in those tables.

You're not understanding. Those are NOT tables. They are fields. Look at what it says in the header. If that stuff was not there, you would be getting all sorts of errors on the site when it tried to use those. If you are still concerned, re-install the product.

Okay, mst_groupmessage, mst_pmtext, mst_profilefieldcategory and mst_usergroup are fields, not tables?

Yes, according to the pic you posted. They are considered columns. But I have been reading it wrong. According to that pic, you are right, they are not there.

Have you tried clicking on the [Ask for Query] link? I would first physically go to the db and make sure they are not there before I did anything, though.

:)
[Ask for Query] isn't clickable.
I manually checked the database and those fields indeed are absent from corresponding tables.

I guess only some manual queries can create those fields. It'd be very helpful for me if someone can tell me that.

Okay..
I got the details from mysql-schema.php, run those queries and everything seems to work fine.

Thanks for your time :)

Glad to here you got it fixed. ;)

Is this mod still fully updated to the latest vb specs?

A bump as nothing has ever been posted since my last question

great mod thank you