It shows that you are unregistered. Please register with us by clicking Here
![]() |
|
![]() |
![]() | Register - FAQ - Today's Posts - New Posts - Support - Search | ![]() |
|
|
#1 (permalink) |
|
Junior Member
Join Date: Jul 2006
Age: 38
Posts: 14
|
So, I am starting a project that has the potential to be a lot larger than anything else that I have done and I need some advice from the experienced...here's the basics...
Users log in to a web site... users belong to a company->companies have projects->projects have docs, etc... previuously all this information had been in one database separtated into tables... so if I have 50 companies on the website and each company has 20 projects and each project has 100 documents...my project documents table starts to get huge (100,000 rows). Would it be wise to separate each company into it's own database? Does this make sense or am I just used to working at too small of a scale? Thanks. Destiny |
|
|
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Free hosting for large files (up to 2Gb/file) | modric | Hosting | 1 | 10-04-2006 10:16 PM |
| Apache breaks with large files | justin | Site and Server Administration | 1 | 09-26-2006 07:34 PM |
| At Large | Anamaru | Graphics & Multimedia | 2 | 09-27-2005 10:10 PM |