[PHP-DB] how many databases should I create
I am developing a variety of different web based systems including inventory, payroll, incident reports etc. Should I create a new database for each project category or one huge database with every table I will ever use in it? -Matt
Re: [PHP-DB] how many databases should I create
Matter of preference really. Do you put all your files in one directory? I do for the most part, but when it comes to security you can divy out access to different databases rather than each table and it makes things simpler, so I use different databases for different projects. Also, I think you can move different databases around onto different partitions if they get too big. -Jeff - Original Message - From: Perry, Matthew (Fire Marshal's Office) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 18, 2004 1:37 PM Subject: [PHP-DB] how many databases should I create I am developing a variety of different web based systems including inventory, payroll, incident reports etc. Should I create a new database for each project category or one huge database with every table I will ever use in it? -Matt -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DB] how many databases should I create
That all really depends on you. I would certainly say that, in general, any given database should only have one users table (with a separate table holding roles, permissions, etc.) In all likelihood - if all of these systems will be working together within a single company, and be built in a common way - you'll likely find it easier to have them all in one system. The counter to that, of course, is that information like payroll certainly shouldn't be easily accessed - so that might be one case where you might want a separate database. You'll really just have to weigh the benefits of having the data together (generally convenience, though there are reasons along the lines of joins and such) with the costs of any lost security or lax in responsibility. - Martin Norland, Database / Web Developer, International Outreach x3257 The opinion(s) contained within this email do not necessarily represent those of St. Jude Children's Research Hospital. -Original Message- From: Perry, Matthew (Fire Marshal's Office) [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: [PHP-DB] how many databases should I create I am developing a variety of different web based systems including inventory, payroll, incident reports etc. Should I create a new database for each project category or one huge database with every table I will ever use in it? -Matt -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] how many databases should I create
On Mon, 18 Oct 2004 14:53:41 -0500, Norland, Martin [EMAIL PROTECTED] wrote: That all really depends on you. I would certainly say that, in general, any given database should only have one users table (with a separate table holding roles, permissions, etc.) In all likelihood - if all of these systems will be working together within a single company, and be built in a common way - you'll likely find it easier to have them all in one system. The counter to that, of course, is that information like payroll certainly shouldn't be easily accessed - so that might be one case where you might want a separate database. You'll really just have to weigh the benefits of having the data together (generally convenience, though there are reasons along the lines of joins and such) with the costs of any lost security or lax in responsibility. shouldn't a good rdbms take care of that though (with reasonable security measures)? can't you get fine grained user privs, at least with a proper db? postgres? Cheers Antoine -- G System, The Evolving GUniverse - http://www.g-system.at -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DB] how many databases should I create
You're talking two different users here - in my instance, I was talking application users, not database users. Yes - realistically - you can use just the one database and have the user permissions for it, it's just a case of making sure you track everything right and don't access the database through the wrong connection - not much different from making sure you access the right database. Realistically - a previous comment hits the nail on the head. All a different database is, in essence, is a different folder - a different place where you can store the same stuff. It's all about how you want to deal with things, how you visualize them and best interact with them. Any database should have sufficient user privs to handle these things, postgresql - mysql - or other. It's all about who the users who can actually access the database are, and how the application will need to map its users to databaes users. Come to think, however - I don't know that you can assign privledges per-table in mysql. So, if your 'user levels' aren't strictly hierarchical - you probably need to break things up (e.g. if payroll shouldn't be able to access inventory). - Martin Norland, Database / Web Developer, International Outreach x3257 The opinion(s) contained within this email do not necessarily represent those of St. Jude Children's Research Hospital. -Original Message- From: Antoine [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 4:02 PM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] how many databases should I create .. chop .. shouldn't a good rdbms take care of that though (with reasonable security measures)? can't you get fine grained user privs, at least with a proper db? postgres? Cheers Antoine -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DB] how many databases should I create
Just to add my 2p/2c.. I use multiple databases as I find this better suits my needs. It is easier to 'plug-in' various components to a client's application if each component is contained in an individual database. For example if your application was to be offered to clients as modules, then dropping in the relevant database would probably be simpler than adding/removing tables from one big database. Also I find it helps me to keep individual client data separate rather than lump it all together and add extra keys to the tables to differentiate between clients. This is of course MY preference for MY application, just airing my thoughts Graham -Original Message- From: Norland, Martin [mailto:[EMAIL PROTECTED] Sent: 18 October 2004 22:12 To: [EMAIL PROTECTED] Subject: RE: [PHP-DB] how many databases should I create You're talking two different users here - in my instance, I was talking application users, not database users. Yes - realistically - you can use just the one database and have the user permissions for it, it's just a case of making sure you track everything right and don't access the database through the wrong connection - not much different from making sure you access the right database. Realistically - a previous comment hits the nail on the head. All a different database is, in essence, is a different folder - a different place where you can store the same stuff. It's all about how you want to deal with things, how you visualize them and best interact with them. Any database should have sufficient user privs to handle these things, postgresql - mysql - or other. It's all about who the users who can actually access the database are, and how the application will need to map its users to databaes users. Come to think, however - I don't know that you can assign privledges per-table in mysql. So, if your 'user levels' aren't strictly hierarchical - you probably need to break things up (e.g. if payroll shouldn't be able to access inventory). - Martin Norland, Database / Web Developer, International Outreach x3257 The opinion(s) contained within this email do not necessarily represent those of St. Jude Children's Research Hospital. -Original Message- From: Antoine [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 4:02 PM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] how many databases should I create .. chop .. shouldn't a good rdbms take care of that though (with reasonable security measures)? can't you get fine grained user privs, at least with a proper db? postgres? Cheers Antoine -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
