views:

208

answers:

2

Hi All,

I have the following requirement. I have with me a database containing the contact and address details of at least 2000 members of my school alumni organization. We want to store all that information in a relation model so that

  1. This data can be created and edited on demand.
  2. This data is always backed up and should be simple to restore in case the master copy becomes unusable.
  3. All sensitive personal information residing in this database is guaranteed to be available only to authorized users.
  4. This database won't be online in the first 6 months. It will become online only after a website is built on top of it.

I am not a DBA and I don't want to spend time doing things like backups. I thought Amazon's RDS with it's automatic backup facility was the perfect solution for our needs. The only problem is that being a voluntary organization we cannot spare the monthly $100 to $150 fees this service demands.

So my question is, are there any less costlier alternatives to Amazon's RDS?

A: 

Hi swapnonil

With out a bit more info I may be way off base here. but 2000 names addresses etc. is not a large DB and I would have thought that the possible use of Amazons RDS was a bit "overkill" to say the least.

Depending on how (and who) you want view edit etc. there are a number of free or almost free alternatives.

One method may be to set up /use a hosting package that has something like phpMyAdmin linked to a mySQL DB. Doing this it is possible to access and edit etc. the DB without having a website front end. Not pretty (like a website front end) but practical. A good host should also back up for you.

Another is to look at Google Documents. OK not really a database more a spread sheet, but very much on the lines of Excel. You can share Google docs with invited people and even set up a small website via Google Docs. This is a free method, but may not be that practical depending on your needs.

Thanks.I should have mentioned that I have a list of 2000 odd names now, but we plan to grow aggressively over the year and should have by then about 6000 members.The problem with normal web hosts is their lack of automation like backups. Most of them are also not really transparent as to how they protect sensitive personal information.
swapnonil
Hi again - OK, I'll still say that 6000 members is a small DB also I think (you don't say) but it appears to only be 1 table."protect sensitive personal information" there are numerous ways to do this and not really upto host. More way DB is designed. Personally I split information from names and passwords/logings etc. and use a salt field to interconnect connect.Automation on back ups (for the sizes you are talking about) could be a very simple script - DB backed up every ... or even before every change by creating a simple txt file in a secure folder
+1  A: 

Hi,

In your case of just contact and address data I would choose Amazon SimpleDB. I know SimpleDB might not be suitable for a large number of tables with relationships and all, but for your kind of data I think SimpleDB is sufficient. And costs is much much cheaper than Amazon RDS.

I also wanted to use RDS, but the smallest db size costs $80 p/month.

Guus