Goal

Although NOSQL seems to be all the rage, particularly MongoDB, traditional RDBMS will never go away. They are too useful. Therefore, to be a full stack developer, you have to know SQL at the journeyman level.

Details

You will be given typical business questions that can be answered with an SQL query.

Treat them like real business concerns you were asked to handle.

Just because the business didn't spell out a requirement doesn't mean you aren't responsible. For example, just because #1 specified sorting doesn't mean you're off the hook for sorting on #3.

In addition, don't give out too much information to the business. The CEO doesn't give a @#$%! about the item id#. For example, #4 should be only one row with the item name and the volume. Again, don't whine about "it doesn't say to include the volume"--that's a huge disfavor you get in school. Ambiguity is the rule in real life. Deal with it. You have to make business decisions in what to report and how to format it.

Make column headers human readable in the result table. In fact, even if they are perfectly human readable, such as "name", change it to "Customer Name" or "Top Grossing Customer"

1)

a. Are any vendors also customers? If so, who?

b. Get me a list of our items by total revenue.

c. Which vendors grossed the most?

d. Which item is in the most orders?

e. Which customers have the most orders?

f. What are our cheapest and most expensive items? What's their volume? What's the price? What's the total revenue?

Setting Up MySQL and Populating the Data

1. The tables are already created and populated at http://sqlfiddle.com/#!9/284793 (Links to an external site.)Links to an external site..

2. Write your queries to answer the questions above.