The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
mysql database repair
I've used the repair / optimize database feature in vbulletin admin panel but these below tables remain at the same size. Is this normal?
Last column is "overhead" which always remain at those values even if I do a repair/optimize Code:
searchcore 14.52 MB 34.08 MB 4.00 MB searchgroup 3.52 MB 4.52 MB 4.00 MB searchlog 5.02 MB 48.0 KB 22.00 MB tagcontent 18.55 MB 34.58 MB 7.00 MB |
#2
|
|||
|
|||
Those tables are innodb or should be unless you changed them from the default vb places on them, a repair/optimize doesnt work on innodb tables, so yes, there would be no change.
|
#3
|
||||
|
||||
How can I convert them to MyISAM safely and do a repair/optimize on them?
|
#4
|
|||
|
|||
You dont need to repair/optimize them, you can do an analyse though, which will report any issues.
If your using the default vb search, i would not run them as myisam tables either, especially if you have a large amount of posts, as they are going to lock. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|