[Jafo232]

Originally Posted by j4ck455

Jafo232, thanks for the reply .

I need to clarify my reasons for wanting|needing a separation of d/bs between WP & vB: it basically boils down to 2 factors - security & server load balancing.

The hosting company we're using for our vB 3.6.4 forum is quite restrictive and a recent request to upgrade from PHP4 to PHP5.2.0 resulted in PHP 5.0.4 being installed & running under CGI in Apache [was not CGI under PHP4], also register_globals is enabled under PHP 5.0.4 [CGI], I have a feeling things are going to go pear-shaped very soon . From a security POV I would prefer to have 2 separate MySQL d/bs for WP & vB respectively, although it probably won't make a huge difference, it might limit some damage.

ITO load-balancing, the option of being able to run a separate MySQL server [b] for WP and other stuff, and keep the PHP for WP & vB running on the same server [a] that vB has its d/b on.

Not sure I agree with everything you stated here, but regardless, it is possible to use two databases I suppose, but you would have to edit the code a bit. Basically, you will have to use the vbulletin database object for any and all calls to the vb data. Probably not that difficult to do, I just personally have no need to create such code.