Create your database with it's three (3) tables. Now, Lahman's data goes all the way back to 1871 and contains a ton of baseball data. Of course, you don't need -- you shouldn't need nor use --- all of it. You can browse the site and download some data. Even if you are not interested in baseball, you can make some sense of the data and come up with a basic database of your own. Here are some parameters to keep things sane:

• Create one (1) database called "baseball"
• Inside this database, create three (3) tables called whatever you want them to be called
• Be creative here and come up with a scenario around which you will base your database and relational tables, for example, you might focus on a particular team, and have a table of 1. players, 2. their batting stats, and 3. their salaries
• Each table should have
• Each table should have
• These limits are to keep the tables relatively small, focus on the structure and format of your tables and the integrity of your data
• You can work from the command line or from phpMyAdmin if you installed it.
• Often times planning your database structure is a helpful, important step. You could use software (Microsoft Excel, Google Docs, etc.) to do this, or you could sketch your ideas out on paper very informally (see examples below). You don't have to turn this document in if you create one