compnet32 Posted November 28, 2006 Share Posted November 28, 2006 I have developed an application that I was soley planning on using for internal use; however, the idea has come up to release it for general use (within my companies territory). The application has several tables, for example a members, products, categories, etc. My question is, should I have a unique member (or company) id and have all the rows held in each table. Or, have different tables for each company with a unique prefix, or have a completely seperate database for each company? The table that will hold the most data is the products table, around 1500+ products per company. Another concern of mine is security, would it be better to separate the data all together into separate tables or databases?Thanks! Quote Link to comment Share on other sites More sharing options...
phpPunk Posted November 28, 2006 Share Posted November 28, 2006 Use the same DB with seperate tables. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.