I think I need to create hierarchical database MySQL for bigger projects in the future.
What should I consider when creating bigger databases?
Can you give me an idea on how to do it?
Can you give links for reference?
Thanks a lot.
How to plan and create hierarchical database MySQL?
Hi,
When creating big databases I think it is very important to consider followings.
-
Usage of the database ( Whether it is a high or low transactional one)
-
Security features of database (This depends on the type of data you are going to use to store.)
-
Pattern of usage. (This means any peak or off peak hours to accessing the database & expected users in different time slogs.)
-
Up time of the database.
-
Size of the database. (Depend on the size of the DB you have to design your tables other relevant fields.
-
How to administer your database.
-
How to upload the data to your database. (Specially initial upload if required)
-
How to back up the data if required.
-
Hardware requirements. (This will depend on all the above requirements)
Further you can refer following web site to get more knowledge (Specially technical stuff) about the designing databases.
Â
How to plan and create hierarchical database MySQL?
Hi,
Any hierarchical data bank type can be an information type where the information is usually sorted in a treelike framework. A business might keep staff information in the table containing attributes/columns for instance staff amount, initially identify, finally identify, along with Division amount.
The business delivers each and every staff along with computers as essential, nevertheless computer system tools may possibly just be used because of the staff to be able to which often it can be given.
The business might keep the actual computer information in the different table that has each and every part's serial amount, variety, along with the staff that employs the item. Generally you must do is usually;
1. Using the database ( Be it a superior or even small transactions one)
3. Safety measures top features of information base (This depends upon the type of information you will definitely employ to be able to keep. )
3. Routine associated with usage. (This means any high or even down high a long time to be able to being able to view the database & estimated people in different time period slogs. )
4. Uptime period in the information base.
5. Measurement in the information base. (Depend on the dimensions of the actual DB you should pattern your own table's other appropriate fields.
6. The best way to dispense computer database.
7. The best way to upload the data to your information base. (Specially primary upload in case required)
8. The best way to backup the data in case necessary.
9. Components prerequisites. (This will depend on each of the earlier mentioned requirements)
It is possible to carry support:
