The goal of this database is to see data about baseball players who have been recently drafted
The goal of this database is to see data about baseball players who have been recently drafted to Major League Baseball Teams. In the MLB there are 30 teams, however, we are not including all of them because this database is mainly for demonstrative purposes.
Each player received a player rating on a scale from 0 to 100 based on their skill level. This score was given by scouts that are hired by each MLB team. The purpose of this rating system is to help MLB teams pick the best players for their program. The database also shows whether the players are represented by agents who let the MLB teams know if they will have to negotiate signing bonus with the agent or the player himself. Phone numbers are also given for each player, agent, and scout to make communication between the parties easy. Players can have only one agent and agents are allowed to represent more than one player but must represent at lease one. Teams can draft more than one player and a player may only belong to one team. Teams may also have more than scout and those scouts belong to that team only who can create more than one scouting report.
Note: As you can see the narrative above is fairly flexible in that you have a lot of room to make assumptions and be creative, and that is the idea - to start with a baseline that you can adapt to another product. Make your own attributes, cardinalities, relationships, or even new tables. However, I'd recommend you start it off by working on these entities: Team, Agent, Player, and Scout.
Part II. DDL
Instruction: Write DDL codes to implement the ERD you have designed by creating the tables with data in SQL Plus. Submit the DDL in a Notepad file (.txt). You can come up with your own data.
Part III. SQL Queries
Instruction: Based on your tables in SQL Plus, create 10 queries of your choice and provide SQL
solutions. You may find it helpful to consult the examples in the SQL exercises. Submit the
queries and their results in a SPOOL file on Canvas.
Note: Do not include any select * from Table; in your queries.
2. Query 2
3. Query 3
4. Query 4
5. Query 5
6. Query 6
7. Query 7
8. Query 8
9. Query 9
10. Query 10
Part IV. Business Summary
summary about your database solution in terms of what it can accomplish and why people should care, preferably in a tone trying to sell it. Highlight the contributions, gains, or pain relievers afforded by your product - the database.