Database Project at work (what to do)
Hi all,
We are currently working on an application that collects user info including fingerprints. For optimisation sake, I'm wondering which is better of these two:
1. Having 1 big database with tables containing all user info and fingerprint data too
or
2. Having two databases, one containing all user info and a seperate database for fingerprints
I'm not a database admin but just a regular IT guy. I'd really appreciate your help guys, I'm here if you need me to be clearer with my question.
We are currently working on an application that collects user info including fingerprints. For optimisation sake, I'm wondering which is better of these two:
1. Having 1 big database with tables containing all user info and fingerprint data too
or
2. Having two databases, one containing all user info and a seperate database for fingerprints
I'm not a database admin but just a regular IT guy. I'd really appreciate your help guys, I'm here if you need me to be clearer with my question.
Comments
-
effekted
Member Posts: 166
Definately not a DBA but from what I've been reading you would have the database normalized so you're not necessarily storing all of the information on a table but across a bunch of tables for performance reasons and etc.
If you're thinking of using 2 databases for security reasons, if you properly secure the server and keep security in mind when creating/setting up the database there is no need to have the data across multiple servers. It's not going to do much if they're not properly locked down, etc.