Hi all,

is it better to have a database for each user who is introducing data in the website or have a table for each user in the same database (in terms of speed for searching)?

I'm asking that because in my server they allow me to have 100 databases and I have ten different users who will introduce data in the website. So I can create ten tables in one database or use a database for each user. In which situation will be faster the communication?

Thank you very much in advance,
Frigopie

neither

and neither will be easy to write queries for

the best solution is one table for all users

Data from users is not correlated at all. I mean users don't need to see what others are introducing. Each one has its own website.

oh, okay then

From what I am reading, each set of tables belongs to a separate website. If this is the case then I would separate them out into different databases.

Yes, exactly. Each database belongs to each different user. I'll do as you said it-iss.com So when Visitors ask for information about userA they will search in DatabaseA and when they ask for userB they will search in database B

Then when visitors navigate in the website, will it be quicker for them?

either
the data is discrete (belongs to one user and one website). in which case a database per website makes sense
OR
the data is used by any / all users in which case it belongs in a single db. (although truth to be told if you are using MySQL and all the db's are on the same db server then it is possible to view all data in all dbs' on that server if required.

if you are acting as an ISP then a single db per website makes sense. if the customer moves on you can just drop that database. any admin task are done on a per db basis

Thank you very much to all!

All databases and websites are in the same server. I'm not acting as an ISP.

the data is discrete (belongs to one user and one website). in which case a database per website makes sense <== That's my case.