CMS Made Simple Forums

I've just done my second installation of CMSMS and when I created the new MySQL database I added the same user as for my first CMSMS database. Is this a good idea, or should I create separate users for each separate CMSMS database? What is considered "best practice" in this regard?

I don't know what best practice is but I try and keep my db login separate especially if they are for different clients. Just in case one client gets the username/password they won't be able to get into other clients sites.

For backup and restoration purposes it'll be a nightmare to try to backup a huge database and figure out what belongs where. If you have a sane hosting provider with 100 databases minimum then keeping it separate is the way to go.

Sounds like you have never tried to delete a database and import it back again for some site operation - try doing that with many db prefixes.

Thanks for your replies.

ajprogramming, when would you need to provide the database user login details to a client? I thought the database user login is only used by CMSMS so it can read and write to the database. Or do you mean that having multiple users/passwords is better for general anti-hacking protection, so if one user password is compromised the other databases aren't at risk?

replytomk3, I think you may have misunderstood my question. I'm not talking about having one large database for multiple websites - each CMSMS website can have its own database, but is it necessary to always create a unique database user for every database? My websites are all running from the same shared hosting, so it seems to be more convenient to add the same database user when setting up a new CMSMS installation, but I'm wondering if there are negative consequences to doing so.

Yes if someone hacks one site then they won't have the others.