I'm starting to dislike my hosting company. My database's recovery method is simple and I'm not allowed to change this. I also can't make backups for two reasons, one is that I don't have enough rights over the computer, and besides SQL disc space is more expensive and they wouldn't know how to meter backups. They tell me that this is very common among Windows web hosting services, and that I have nothing to worry about because they're responsible for keeping the server running, have air conditioners and temperature alerts, are very careful about patching the server, etc. None of this would stop a torn page, though.

So is it true? Is this just something we live with, the cost of having a database up in the sky? Am I the only one worried about a catastrophic failure?

Should I find a new host, come up with a script to download copies of my data for backup, or start taking prozac and stop worrying about it?

If I have to make my own backup script, and I better off selecting * for xml, or downloading MSDE / SQL Express and setting up a linked server, then selecting * into something local?

If they don't allow you to make backups of your database you should find a new host. This is an appauling policy for a host to have.

I usually ty to back mine up weekly through phpmyadmin.

Tell your host (pardon the French) that they're totally, unequivocally, and completely full of crap.

ANYTHING can be backed up, including SQL Server (I'm assuming that's what you mean by SQL) databases. It's just a matter of configuring the backup device (usually a tape drive, but sometimes external hard drives can be used...it really doesn't matter as long as it works, IMHO) and away you go. SQL Server does have backup capabilities as well, although I haven't used them personally (my host set all that up for me) so I don't know how exactly they work.

Look at it this way:

1) An SQL Server database, or any database for that matter, contains data.
2) That data is stored on a hard drive.
3) Hard drives are easy to back up on a Windows server.

Like st0x said, that's a disgusting policy for any host to have. What happens if the hard drive goes in the server? Or if it's in a RAID configuration and they all go (don't laugh...I've seen this happen before)? You're up the creek and chances are your host won't assume a red cent's worth of responsiblity.

If I were you, I'd be looking at a new host as of 5 minutes ago, dude. Someone's sticking the screws to you, bigtime.

( also know (having read your posts) that you don't like to call people out, and I can understand why. In this case, though, I think a callout is in order. That way, other people looking at that host (or using that host) don't get screwed.

As far as a recommendation for a host goes, check out Sectorlink. They do 7-day rolling backups on their servers (I think it's an extra $25 for dedicated servers per month...I really should look at my next bill and find out), and they don't screw around.

How much do you know about the server configuration? If they're using stripped raid, with no mirroring ( and they very well could be - this provides speed, or more hosting accounts per server, and is less expensive than stripped and mirrored ) I'd be really concerned. I had this setup in a laptop, and when it died, well, I still haven't sent it in for service, because I'm afraid they'll re image the drives. And I can't recover them myself, not knowing how the data is split up, exactly.

Like Adam said, SQL Server has online backup functionality built in. You can do this either as a SQL command, or through the UI ( Enterprise Manager or SQL Mgt Studio ). The backups it generates are just regular files, not locked by the server, or really associated with SQL any more than a page about how to write a query. There's no reason they should charge extra for this.

It probably wouldn't hurt to work out your own off-site backup system either way. If you back up your database to the same drive it lives on, that only gives you so much protection. I'd use XML instead of linking the two servers, mostly because if you use SELECT INTO that's a distributed transaction. I'd also make sure you have a script of the entire schema - indexes, constraints, stored procedures, views, users, permissions, all that. If you go that route, post a message in here ... I've got some experience with all this.

I've never heard of a torn page in practice. You probably don't need to worry about that one, although you should still have full control over your data, including being able to make backups.

gotta get a new host. if i couldnt backup my db i would go crazy. i have a cronjob setup to auto backup then i just download it once a week and burn it onto a dvd.

even with ideal conditions, a power surge could knock out a whole bank of raid hds, that happened before......

Originally Posted by ADAM Web Design

( also know (having read your posts) that you don't like to call people out, and I can understand why. In this case, though, I think a callout is in order. That way, other people looking at that host (or using that host) don't get screwed.

I thought I was getting screwed. I'm REALLY tempted to out these people, and I think it would be the right thing to do. I'm worried that that would open up the possibility of a slander or libel suit against Web Master Talk for allowing me to defame the character of this company, though. No good deed goes unpunished, and it would be bad enough to bring misery on myself, but with the luck I've had, I would manage to get the site shut down. And everybody would hate me.

For what? Presenting your side of the story?

Dude, it happens all the time. If that's what they told you, then as long as you don't call them a liar or a thief or a criminal or something like that, it's not slander.

Besides, no host would be stupid enough to sue a community board. If they did, they'd lose bigtime. The hosting business is dominated by, ruled by, and fueled by geeks, and geeks are just looking for an excuse to be self-righteous and pissed off about something.

Do it, bro. We'll back you.

I agree with the others who posted how outragious your hosting company is treating you.
My suggestion (which I haven't seen mentioned) is switch to Linux hosting. Try it you'll like it.

Obviously you haven't read some of our boy's posts, or you'd know he rocks the .NET action.