The Parch & Posey Database

 

The Parch & Posey Database


Entity Relationship Diagrams


An entity relationship diagram (ERD) is a common way to view data in a database. Below is the ERD for the database we will use from Parch & Posey. These diagrams help you visualize the data you are analyzing including:


  1. The names of the tables.
  2. The columns in each table.
  3. The way the tables work together.

You can think of each of the boxes below as a spreadsheet.

What to Notice


In the Parch & Posey database there are five tables (essentially 5 spreadsheets):


  1. web_events
  2. accounts
  3. orders
  4. sales_reps
  5. region

You can think of each of these tables as an individual spreadsheet. Then the columns in each spreadsheet are listed below the table name. For example, the region table has two columns: id and name. Alternatively the web_events table has four columns.

The "crow's foot" that connects the tables together shows us how the columns in one table relate to the columns in another table. In this first lesson, you will be learning the basics of how to work with SQL to interact with a single table. In the next lesson, you will learn more about why these connections are so important for working with SQL and relational databases.


Supporting Materials


Want to Load the Parch & Posey Database into a Local Postgres Environment?

Workspaces are available for all of the SQL exercises and projects in this course, but if you want to run load the Parch & Posey database into a local PostgreSQL server, you can find the database file (supporting materials - Parch & Posey Database).


Setting up the Parch & Posey database


The Parch & Posey database will be used for most of SQL the exercises in this course. You can create and populate the database using PostgreSQL with this code:


$ createdb parch
$ psql parch < parch_and_posey.sql

Comments

Post a Comment

Popular posts from this blog

Entity Relationship Diagrams

Image
  Entity Relationship Diagrams From the last lesson, you might remember that an  entity relationship diagram  (ERD) is a common way to view data in a database. It is also a key element to understanding how we can pull data from multiple tables. It will be beneficial to have an idea of what the ERD looks like for Parch & Posey handy, so I have posted it again below.  You might even print a copy to have with you as you work through the exercises in the remaining content. Tables & Columns In the Parch & Posey database there are 5 tables: web_events accounts orders sales_reps region You will notice some of the columns in the tables have  PK  or  FK  next to the column name, while other columns don't have a label at all. If you look a little closer, you might notice that the  PK  is associated with the first column in every table. The  PK  here stands for  primary key .  A primary key exists in every table, and...
Read more

Arithmetic Operators

  Arithmetic Operators Derived Columns Creating a new column that is a combination of existing columns is known as a  derived  column (or "calculated" or "computed" column). Usually you want to give a name, or "alias," to your new column using the  AS  keyword. This derived column, and its alias, are generally only temporary, existing just for the duration of your query. The next time you run a query and access this table, the new column will not be there. If you are deriving the new column from existing columns using a mathematical expression, then these familiar mathematical operators will be useful: *  (Multiplication) +  (Addition) -  (Subtraction) /  (Division) Consider this example: SELECT id , ( standard_amt_usd / total_amt_usd ) * 100 AS std_percent , total_amt_usd FROM orders LIMIT 10 ; Here we divide the standard paper dollar amount by the total order amount to find the standard paper percent for the order, and use the  ...
Read more

NOT

  NOT The  NOT  operator is an extremely useful operator for working with the previous two operators we introduced:  IN  and  LIKE . By specifying  NOT LIKE  or  NOT IN , we can grab all of the rows that do not meet a particular criteria. Questions using the NOT operator We can pull all of the rows that were excluded from the queries in the previous two concepts with our new operator. Use the  accounts  table to find the account name, primary poc, and sales rep id for all stores except Walmart, Target, and Nordstrom. Use the  web_events  table to find all information regarding individuals who were contacted via any method except using  organic  or  adwords  methods. Use the  accounts  table to find: All the companies whose names do not start with 'C'. All companies whose names do not contain the string 'one' somewhere in the name. All companies whose names do not end with 's'. Solutions to NOT...
Read more