Database Structure

[sladmin]

Ok, so you're probably sick of me creating new threads recently, but they do all relate to one website.

This website is going to be pretty huge as far as I can tell, multiple areas requiring dynamic content. Not only that but there will also be 3 types of users. Let me explain a bit more...

My site will have 3 areas requiring different types of users: 1) Classifieds 2) Business Directory 3) Village Directory.

At the moment I am very confused about how to design my database(s). The main areas of the website so far are:
Village Directory
Business Listing
Classified Directory
Tourism (including attractions, accommodation plus loads more.)
Entertainment (including shows, gigs, concerts, days out ect)
Guides & Tips
News
Advertising
Plus a few other bits and bobsProblem is, because there are quite a few main areas (some of which will have dynamic content fed from a db) I have no idea how to organise all of this data. Do I have more than one database for the different areas or do I have one large database?

Also because there are probably 3 different types of users do I have one table for users but include access levels or have separate tables and link them to other tables?

I'm sorry if this seems like a large question to ask but this is something I can't really mess up halfway through the website. Once this database has been designed and the website is being built I'm not going to rebuild it for a long time.

If you need any more information then hit me up on MSN, private message or just post here.

Big Thanks in advance,

[Carl Shepherdson]

What database technologies are you going to be using?

[sladmin]

I'm going to be using MySQL & ASP VB

[sladmin]

I'll also be using DSN-Less connections too. Not sure if that will help anyone.

[Andrew Taylor]

I'd go for one large database rather than multiple ones

And then one user table with access levels listed

Let me know if you need any help with it