XenForo => vBulletin 4 => vBulletin 5 = Headache + Big DB size

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • John Hide
    New Member
    • Jan 2016
    • 11
    • 5.1.x

    XenForo => vBulletin 4 => vBulletin 5 = Headache + Big DB size

    Hello,

    This weekend, I began my journey to migrate XenForo to vBulletin.
    filthy I did not find way to pass directly XenForo to vBulletin 5, so I had to first install the vBulletin 4, import (ImpEx+XenForo Alpha plugin), and finally upgrade to vBulletin 5 (with various errors in between)

    However, and although the process could have taken 6hs, took 48 hours ¬¬, the size of the database also increased suspiciously.

    In XenForo the database occupied 1.8 GB.
    Now with vBulletin 5 database occupies 3 GB.

    Some of the reasons for increase are:
    closure (800MB)
    node (590MB)
    searchcore_text (820MB)


    The post, which should be the biggest, it is not so...
    post (460MB)

    - Because they are so important as to double the size of the database?
    - Because vBulletin product is "paid" why not offers official import tools of quality? or it is only designed for novice people who install the first forum?


    Thanks
    Last edited by John Hide; Sun 31 Jan '16, 2:28pm.
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24287
    • 6.0.X

    #2
    The post table is not used in vBulletin 5, it's a remnant from vBulletin 4.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • anfimovir
      Member
      • Jul 2006
      • 49
      • 3.8.11

      #3
      Already fixed in:

      Comment

      • John Hide
        New Member
        • Jan 2016
        • 11
        • 5.1.x

        #4
        Thank you very much for the information.

        Upgrade error? I use 5.2.0 Patch Level 1

        Comment

        • anfimovir
          Member
          • Jul 2006
          • 49
          • 3.8.11

          #5
          No, this fix is scheduled in 5.2.1

          Comment

          Related Topics

          Collapse

          Working...