storing ALL content in a database - issues?

[weezil]

I have generally designed sites where most of the content is stored in individual HTML files, and the only database I use is for things like newspostings.

For the next website, a commercial 100ish page (SQL Server 2000) site I'm thinking of storing all the content in a database to help organise things better. Are there any issues with doing this, like the fact that you'll have to query the database for every page requested? Does that put a large strain on the server? We aren't antisipating a large number of people visiting - maybe 100-200 a day tops. Cause It's the clients server, I don't want to be responsible for bringing it down!

Any thoughts much appreciated🙂

Chris.

[[deleted]]

If you are only looking at 100-200 visitors a day, it really won't make a difference. The database server can handle that no problem at all.

But, if you are interested in storing all your data in a database and having less load on the server for higher use systems, you might consider caching the database results to disk and just refreshing them occasionally...

http://zend.com/zend/spotlight/code-gallery-wade4.php