WoodiE
Fri 9th May '03, 8:40pm
Ok in the last month or so I have been receiving database errors from time to time, I'm 90% sure it was cause of a mistake I made when running a query on the database then realized it was supposed to be two different queries.
None the less, I now get random database errors and such. So this is what I was thinking. Installing vBulletin 2.3.0 clean on a brand new database, copy over the users from the old database to the new so I don't lose any members and they won't have to re-register, then take the old database and some how tie it in with the new vBulletin board, BUT making the old database read only. There is a lot of good info on the existing forum, and I'd REALLY hate to just delete it like it didn't matter. I'd rather just find some way of repairing the current database back to health before just deleting it.
Is this possible? Running one database as the main database, but still allow members to read only the old threads and posts from the current database.
-Michael
None the less, I now get random database errors and such. So this is what I was thinking. Installing vBulletin 2.3.0 clean on a brand new database, copy over the users from the old database to the new so I don't lose any members and they won't have to re-register, then take the old database and some how tie it in with the new vBulletin board, BUT making the old database read only. There is a lot of good info on the existing forum, and I'd REALLY hate to just delete it like it didn't matter. I'd rather just find some way of repairing the current database back to health before just deleting it.
Is this possible? Running one database as the main database, but still allow members to read only the old threads and posts from the current database.
-Michael