I'm going to have to kill someone at my web hosting company
This is the third time this week I have suffered a debilitating db error!!!
The worst thing is that I can't access my website tools from work because the corporation blocks everything but port 80!
So, I go over to the library for lunch to fix my db and the web server is so bogged down that I can't do anything!!!
I've just wasted an hour to repair one table. I can't even run a check to see what tables are corrupted!!!
I'm looking for a new hosting company, I can't take this anymore...
Comments
In this case... I spent an hour but was repeatedly logged out our timed out of the server!
Under normal circumstances I can fix the trouble in a couple of minutes. I can't fix it when they have the server down "being worked on"!!! To make matters worse, no where on their website can you find the status of a server!
I think I just ended up on a bad shared server. They offered to move me to a different server, but at a price! You don't wreck some one's car then offer them a deal on a news one!
The only db that ever has problems is the one for my blog, the other three are fine. It's always one of two db's that get corrupted.
One of them is the visitor table. If the server goes down in the middle of a transaction it breaks. Because everything uses that table for tracking visitors and what they do if it breaks the site will not work.
The other table is the one where my entries are stored. Today, the server went down while I was in the middle of updating an entry...
For the longest time (before I started blogging) my site had very low traffic, between 50 and 100 hits a day bunched within a few hours of time. Now, I get several thousand hits a day and I'm beginning to realize that the blogging software I chose may not be up to the task. I've already had to empty the visitor table when it passed the 85K entries mark!
What's holding me back from switching to something else is that I still get a very steady stream of visitors via StumbleUpon and Google. If the blog URLs change all of that traffic will go away as they will get 404 errors...
When I ran the site for Kenzer & Company I very rarely (twice a year) had a database issue.
One issue was a corruption in the visitor table for the store and the other was when the main post table in our forums was lost...
The first trouble was fixed in 1 minute, the second required finding the backups and restoring from them. The bad part about it was that the db error happened just before the nightly backup routine....