 |
 |
 |
 |
|
|
|
Comments for: tim20010117
| Message # 1013666: |
|
Date: 10/06/02 10:48
By: Kapil Subject: MULTIPLE TABLES OR HUGE TABLES-BETTER OPTION? We are creating an application for online use which consists of 4 levels of masters: a. Level1 - CompanyName b. Level2 - CompanyExecutive c. Level3 - Company's Executive Clients - Corporate d. Level4 - Client's Employee - Client Level1 data is not sharable... i.e., a person can not see data of two companies together... they are two separate entities with no relationship with each other... The total data per company is expected to be: 1 company x 50 Executives x 50 corporates per executive x 20 clients per corporate x 20 orders / forms per client - 1,00,000/- orders, which is likely to grow with time. Total no. of tables involved per company = 10 tables The total no. of companies expected is >200... So, we have two alternatives... one add a field for companyname in all the tables... or ... create separate tables for each company with companycode as suffix... eg., Orders2556 where "orders" is table name and "2556" is companycode... and store data accordingly or put a flag field "CompanyID" in all tables... Kindly suggest... because there are going to be a whole lot of queries executed on the same server... Also, if we keep all records in the same table and do some partitioning etc., (i dont know if sql server supports it properly), would it be advisable to put it in the same table as against creating so many tables ... i.e., 20 common tables + 200 companies X 10 tables per company i.e., 2000+ tables |
Previous Message | Next Message |
| Comments: | ||
| full theory about database transactions ?? | Girish Agarwal | 01/27/05 00:36 |
| RE: excellent article | Lance Edusei | 07/14/04 08:30 |
| RE: MySQL Transactions | Rob Limbrey | 01/21/03 08:45 |
| MySQL Transactions | Imtiaz | 10/16/02 06:22 |
| MULTIPLE TABLES OR HUGE TABLES-BETTER OPTION? | Kapil | 10/06/02 10:48 |
| please found out my code mistakes | Mary Pei | 10/04/02 05:44 |
| project work please help us | mike smith | 09/11/02 06:51 |
| RE: Transaction in MySQL | Pedro Salgado | 08/13/02 07:12 |
| PostgreSQL nested transactions | Lonny L GRanstrom | 08/09/02 22:36 |
| RE: How to trigger Rollback | Vinco | 07/07/02 01:55 |
| How to trigger Rollback | Igor | 04/25/02 23:46 |
| What about batch updates? | pedro | 03/10/02 20:41 |
| LDAP "Rollback" | Fraser | 02/06/02 20:57 |
| nested transactions - my solution | Shivers | 08/17/01 12:57 |
| PHP, MSSQL7 and Transactions | Andrew Prior | 04/25/01 05:47 |
| XML and pgSQL | moses | 03/06/01 14:09 |
| RE: transactions... | george | 02/07/01 06:29 |
| transactions... | michael kristopeit | 02/05/01 11:35 |
| RE: MySQL Transactions | Ryan Ayers | 01/30/01 22:41 |
| Clean solution to nested transactions | Jeffrey Greer | 01/28/01 16:43 |
| RE: sessions and DB transactions | Kai Meder | 01/27/01 18:37 |
| RE: MySQL Transactions | Kai Meder | 01/27/01 18:35 |
| sessions and DB transactions | John Harnett | 01/26/01 23:17 |
| nextval/currval in postgres | Don Baccus | 01/26/01 20:54 |
| Transactions in functions vs. Postgres | Don Baccus | 01/26/01 20:46 |
| Re: I hate duplicate functions. | Kirk Parker | 01/24/01 19:20 |
| RE: nested xactions | Peter Moulding | 01/24/01 17:24 |
| RE: excellent article | Peter Moulding | 01/24/01 17:18 |
| RE: Transaction in MySQL | Mattias | 01/23/01 05:28 |
| RE: nested xactions | JBW | 01/22/01 23:37 |
| Transaction in MySQL | Habibi | 01/22/01 18:22 |
| MySQL Transactions | Ryan Ayers | 01/22/01 14:30 |
| excellent article | Ryan McGeary | 01/22/01 09:35 |
| nested xactions | Jim G | 01/22/01 08:48 |
| Ideas | Andrew Coldham | 01/22/01 03:49 |
|
If you are looking for help, please post on the appropriate forum here. Your questions will be answered much more quickly. | ||
