Hi, we're a small non-profit and are looking into building a database but are quickly becoming overwhelmed with the possibilities. Could anyone suggest if it's better to host online, or get a NAS or server to host here? We were leaning towards getting a NAS to serve the database and act as a file server (because it seems the least expensive solution), but would like to hear some more expert input. Thanks in advance!

A database of what?

Could anyone suggest if it's better to host online, or get a NAS or server to host here

It depends.
Is it for WAN or website use?
is it for LAN desktop use only?
or a combination of both?

We were leaning towards getting a NAS to serve the database and act as a file server

Bit of a wide ranging question this
If the database format is a stand alone file based system (Access .mdb or dBase .dbf etc or flat file) then theoretically a NAS would be ok.

However if the database requires active indexing and retrieval prior to client access (SQL Server, Oracle, MySQL etc) then a NAS is not going to be running a suitable OS ( Windows or a *nix variant ) (most NAS devices run on the embedded SnapOS) and then you will need a file and database server

Is this going to be a web database? Do you have a web server? What does your computer network look like? Are you using a lot of Microsoft, or mostly open source? You'll get much better answers ( because the question is very broad ) if you tell us a little bit about your system, and what the database needs to accomplish.

Thanks a lot for the replies.

Our network consists of 6 users using iMacs, plus an old G3 acting as a file server. Our website is hosted online. Our database is going to be accessed primarily by users on our network, with occasional offsite access required when an employee is on the road (not too frequently, we're only 5 people).

We are deciding between using FileMaker or MySQL.. if you have any advice to help us make this decision as well, we would appreciate it greatly.

Thanks again.

FileMaker isn't a serious database application. You can get a little bit done with it, but as your needs get more complex, it starts to fall short. But it's much, much harder to find any help for FileMaker than MySQL. People take that seriously, so people have already tackled similar problems and can give you some advice.

If your web site is hosted with a Linux server somewhere, possibly in another state, use the MySQL database that comes with it. It doesn't really matter how often people need to use it from outside your network. Just if people need to do it every now and then, you need to be able to do that.

Just if people need to do it every now and then, you need to be able to do that.

First making sure that the hosting co will open TCP port 3306 through the firewall for your IP

Originally Posted by chrishirst

First making sure that the hosting co will open TCP port 3306 through the firewall for your IP

Good point. If you write all the code and it's blocked by a firewall, that's about the most difficult thing in the world for a programmer to debug.

I dont think maintaining an off-site database is going to be easy for you. you'll end up paying more in terms of administration and debugging.
I would advice, stick to the "on-site" localhost mysql server. It will be easiest to maintain.

The second option is to create a "locally accessible" website only. If anyone of you is outside the network, that person DOES NOT get access to the website/data.

Maintaining an off-site db server or a automatically synced server is not going to help you save money.
--Amit.