Mysql database design

Databases
1

Looking for any suggestions or advise or even best practices.
I have developed an online database using php and mysql. It allows companies to log complaints and resolutions etc. There is a user database for login and a cip database for logging the main data. 2 companies are trialing and testing the database. At the moment each company is using separate databases and separate html pages. I am wondering what the best way to add more companies.
Ideas that I have are:
To have one large database for users and one large database for cip and use a company id or similar to identify individual companies records in the database.
To use the same html pages for every company but select which database to use from the login details. So that each company will have a separate cip database but all companies use the same users database.
Or just keep everything separate for every company. (this might be really bad for doing updates)

I hope I have made myself clear and look forward to any suggestions.

Thanks

2

Thanks for your reply.
Just to clarify…
So should I use company_id with option 1 or 2?

To have one large database for users and one large database for cip and use a company id or similar to identify individual companies records in the database.

To use the same html pages for every company but select which database to use from the login details. So that each company will have a separate cip database but all companies use the same users database.

Thanks

3

use the company_id

4

maybe I need to say table instead of database. So 1 database with 2 tables - 1 table for user details and 1 table for main info…and maybe more tables for company details etc.
Sorry about any confusion
I think the main point I wanted clarified was to use 1 database for every company that will be using the application.

5

thanks for your help…on both forums :slight_smile:

6

option 1

7

interesting…

I would have suggested running one db for the lot because (I thought), splitting into two dbs mght fall under premature optimisation, which is not good.

bazz