Database error
Senior Member
Joined: Feb 2012
Posts: 171
Likes: 4
From: Caledonia, Ontario
i think he pretty much means that when that database error pops up, there's too many people on the site, or trying to access that certain page, and the website can't handle it. so when the page becomes available to use again (and isn't maxxed out) it lets you back on, which explains why we have to keep waiting to get onto the page.
Senior Member
Joined: Feb 2012
Posts: 3,770
Likes: 2,178
From: SE Michigan
No habla ineptitudo.
When you configure a database (the forum software, vBulletin, uses a database called mySQL), you configure it based on a number of hardware and software factors. One of the things you have to do is decide how many concurrent connections (multiple requests to the database at the exact same time) it will support.
If these forums are being hosted on a shared server (many web sites running on the same physical server), then the hosting company usually limits each account to a maximum number of concurrent connections. If the maximum threshhold of concurrent connections is exceeded, those users (page requests) over the max will see those database error messages. Once some of the previously active requests are complete, the next requests in line can get in (that's why the site eventually 'starts workin again' for you.
It's like a 50 people trying to get through a half dozen standard sized doors at the same time - only 6 people or so can get through at the exact same time (concurrently), and everybody else must wait (get the error message) until those ahead of them get through the door.
When you configure a database (the forum software, vBulletin, uses a database called mySQL), you configure it based on a number of hardware and software factors. One of the things you have to do is decide how many concurrent connections (multiple requests to the database at the exact same time) it will support.
If these forums are being hosted on a shared server (many web sites running on the same physical server), then the hosting company usually limits each account to a maximum number of concurrent connections. If the maximum threshhold of concurrent connections is exceeded, those users (page requests) over the max will see those database error messages. Once some of the previously active requests are complete, the next requests in line can get in (that's why the site eventually 'starts workin again' for you.
It's like a 50 people trying to get through a half dozen standard sized doors at the same time - only 6 people or so can get through at the exact same time (concurrently), and everybody else must wait (get the error message) until those ahead of them get through the door.
Senior Member
Joined: Feb 2012
Posts: 3,770
Likes: 2,178
From: SE Michigan
Are you on a shared or dedicated server?
Max connections depends upon your available RAM. The is a formula - your techies should be able to determine the most optimal setting (*if* this is even the issue - remember, I was just making a suggestion based on common issues like this).
Last edited by roadPilot; Feb 29, 2012 at 10:24 PM.
