Fix MySQL Database
Budget: $250 – $750 USD
Add fields and edit existing fields, add relations and foreign keys.
Here are the problems I need solved.
1. The database is lacking relations, there are no foreign keys, meaning that every update and delete queries can’t cascade and must be done in separate queries, which in turn will in turn will make more load on the server and the website reducing it’s speed.
2. Please check the attached files “johnfcur_firearm.pdf” for the database schema and “Diagram 1.png” for a diagram of the database, please note that there are no connections between the table for the lack of foreign keys.
• Scalability:
o Any change in the database structure in the future for adding or optimizing features is going to be harder the more the website is used, that’s because of that the database lacks relations and a good structure.
o The database and the website are using the same database, which means that server resources are shared between them, and the server have to handle both.
o The database can handle the storing of records in it, the issue is not how much it can store, the issue is that it will slowdown dramatically the more it stores and that’s because there are redundant data and the structure can be more efficient.
o Concurrent users number in the future will be a major issue and the website will slow down dramatically and that’s because of the redundant and extra process in the backend that can be skipped as they are only there because of the bad database structure.
Here are the problems I need solved.
1. The database is lacking relations, there are no foreign keys, meaning that every update and delete queries can’t cascade and must be done in separate queries, which in turn will in turn will make more load on the server and the website reducing it’s speed.
2. Please check the attached files “johnfcur_firearm.pdf” for the database schema and “Diagram 1.png” for a diagram of the database, please note that there are no connections between the table for the lack of foreign keys.
• Scalability:
o Any change in the database structure in the future for adding or optimizing features is going to be harder the more the website is used, that’s because of that the database lacks relations and a good structure.
o The database and the website are using the same database, which means that server resources are shared between them, and the server have to handle both.
o The database can handle the storing of records in it, the issue is not how much it can store, the issue is that it will slowdown dramatically the more it stores and that’s because there are redundant data and the structure can be more efficient.
o Concurrent users number in the future will be a major issue and the website will slow down dramatically and that’s because of the redundant and extra process in the backend that can be skipped as they are only there because of the bad database structure.