Forum Moderators: open

Message Too Old, No Replies

Database Security

should databases be segregated or all combine into one

         

norek

6:11 am on Feb 22, 2006 (gmt 0)

10+ Year Member



Setting up a program relying on MySQL db...

Which is better?

- Seperate public info, from private info, from financial info into multiple databases?

- Seperate public info, from private info, from financial info into multiple tables within a single database?

The entire website will have different features that will require different information, where sometimes, the information required will be either private, public, or financial...

WHAT ARE THE PROS AND CONS OF EACH OF THE ABOVE?
Example: is one method slower? harder to setup? in terms of security, does either method really matter?

physics

3:09 pm on Feb 23, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I think multiple databases (with different uname/pass) will be more secure. I guess it's less convenient but seems like a good idea to me.

aspdaddy

5:50 pm on Feb 23, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I always use the principle of separation when designing systems. Separate out the high/low volume, known/unknown users, business critical data/non-business critical data, current/archive transactions.

The cons are cheaper and less secure the pros are expensive and more secure - what reputation do you want for yourself - cheap or secure :)