Ask yourself some questions before you get to the SQL. You have a table you've called BoatBooking, so presumably we are booking (making reservations) for a boat by someone for some purpose. So.....

1. Can a customer book different boats at different times?

2. Can a single boat have more than one name and length at the same time? If not, where do the independent boat parameters belong?

3. Does customer information (name, address, phone) depend on which boat they've booked?

4. Can a skipper work on different boats at different times?

5. Can someone crew on different boats at different times?

etc.

Every time one of these questions will help you think about which attributes (name, length, date, etc.) are dependent on -- or independent from -- others. Which in turn will help you think about whether those attributes belong in the same table or not.

Good luck,

Rich