2. PHPRunner General questions
  3. Ideas on table contruction for large amount of data
This topic is locked

Ideas on table contruction for large amount of data

 		6/19/2014 2:02:17 PM
PHPRunner General questions
M
 mmponline author

I need to construct a large database with a long application form (many fields) and lots of records. (6000+)
One thought would be to have all data field as one large table.

The other would be to break some data down(Eg. all address information)into smaller tables and relate them with the main table.

The main disadvantage (I think) of the smaller tables with related info, is that it would be difficult to run a search to find information, as all information would not be in one table. Also for queries. On the other hand, one large table might be slower although searches would be quick. I'm not sure and open for suggestions. Further, if the main table as a lot of links to the related info, won't in influence the speed as well.

Please give some ideas on how to ensure fast retrieval of data and or workability and functional construction of the data.

Any help appreciated.
A
 		Abul 6/21/2014



I need to construct a large database with a long application form (many fields) and lots of records. (6000+)
One thought would be to have all data field as one large table.

The other would be to break some data down(Eg. all address information)into smaller tables and relate them with the main table.

The main disadvantage (I think) of the smaller tables with related info, is that it would be difficult to run a search to find information, as all information would not be in one table. Also for queries. On the other hand, one large table might be slower although searches would be quick. I'm not sure and open for suggestions. Further, if the main table as a lot of links to the related info, won't in influence the speed as well.

Please give some ideas on how to ensure fast retrieval of data and or workability and functional construction of the data.

Any help appreciated.


You have to break down the whole database into several related tables. I don't see any other options except that fro your case. But for your 2nd problem you could run several queries for getting required info from several related tables. I think this is the basic theory for a relational database based phprunner project. Learn first how to design an workable relational database schema then go forward.
HJB 6/21/2014

Thanks to the developers, built-in TABS and SECTIONS features can be implemented that way, even larger amounts of fields can be ergonomically handled on an application process without any loss of visual oversight.
M
 		mmponline author 6/26/2014

Thank you both for your feedback. I have a bit of knowledge for related tables. I'm just not sure how one would run several queries to retrieve search results from the main table as well as the related tables.
IOW
Main
Related:

Address details

General info

Directors

Documents
When I run the search, I would then hope to find results whether it's in any of these table. Not sure how.
Walk2fly. - I agree! Since a few upgrades ago, one can now easily add related info into the same design and it looks like one huge table. That's very handy. Just not sure about the searches...
Sergey Kornilov admin 6/26/2014

This sort of question is not easy to answer without knowing all the details of how this data will be used. Just an idea - you can use dashboards feature in PHPRunner 8 to run a search across several related or even non-related tables at once.
M
 		mmponline author 6/26/2014

If that's the case, I will definitely upgrade from 7.1, as I do need this feature. This will help me to break down the table into bits.

IS this feature available in Enterprise version as well, as I will need the custom reports and other features currently in Enterprise. Will (Is) all features in 8.1 available in Enterprise as well?