Cleaning a PostgreSQL Database
In this project, you will work with data from a hypothetical Super Store to challenge and enhance your SQL skills in data cleaning. This project will engage you in identifying top categories based on the highest profit margins and detecting missing values, utilizing your comprehensive knowledge of SQL concepts.
Data Dictionary:
orders:
orders:| Column | Definition | Data type | Comments |
|---|---|---|---|
row_id | Unique Record ID | INTEGER | |
order_id | Identifier for each order in table | TEXT | Connects to order_id in returned_orders table |
order_date | Date when order was placed | TEXT | |
market | Market order_id belongs to | TEXT | |
region | Region Customer belongs to | TEXT | Connects to region in people table |
product_id | Identifier of Product bought | TEXT | Connects to product_id in products table |
sales | Total Sales Amount for the Line Item | DOUBLE PRECISION | |
quantity | Total Quantity for the Line Item | DOUBLE PRECISION | |
discount | Discount applied for the Line Item | DOUBLE PRECISION | |
profit | Total Profit earned on the Line Item | DOUBLE PRECISION |
returned_orders:
returned_orders:| Column | Definition | Data type |
|---|---|---|
returned | Yes values for Order / Line Item Returned | TEXT |
order_id | Identifier for each order in table | TEXT |
market | Market order_id belongs to | TEXT |
people:
people:| Column | Definition | Data type |
|---|---|---|
person | Name of Salesperson credited with Order | TEXT |
region | Region Salesperson in operating in | TEXT |
products:
products:| Column | Definition | Data type |
|---|---|---|
product_id | Unique Identifier for the Product | TEXT |
category | Category Product belongs to | TEXT |
sub_category | Sub Category Product belongs to | TEXT |
product_name | Detailed Name of the Product | TEXT |
As you can see in the Data Dictionary above, date fields have been written to the orders table as TEXT and numeric fields like sales, profit, etc. have been written to the orders table as Double Precision. You will need to take care of these types in some of the queries. This project is an excellent opportunity to apply your SQL skills in a practical setting and gain valuable experience in data cleaning and analysis. Good luck, and happy querying!
-- top_five_products_each_category
WITH inner_query AS(
SELECT
p.category, p.product_name, ROUND(SUM(o.sales)::numeric, 2) AS product_total_sales, ROUND(SUM(o.profit)::numeric, 2) AS product_total_profit, RANK() OVER(PARTITION BY p.category ORDER BY SUM(o.sales) DESC) AS product_rank
FROM orders AS o
INNER JOIN products AS p
ON o.product_id = p.product_id
GROUP BY p.category, p.product_name
)
SELECT category, product_name, product_total_sales, product_total_profit, product_rank
FROM inner_query
WHERE product_rank <= 5
ORDER BY category ASC, product_total_sales DESC
-- impute_missing_values
WITH cal_unit_price AS (
SELECT product_id, quantity, profit,
(SUM(profit::numeric)/SUM(sales::numeric)) + SUM(discount::numeric) AS unit_price
FROM orders
GROUP BY product_id, quantity, profit
),
cal_quantity AS (
SELECT product_id, quantity,
CASE
WHEN quantity IS NULL THEN ROUND(SUM(profit::numeric)/SUM(unit_price::numeric))
WHEN quantity IS NOT NULL THEN quantity
END AS calculated_quantity
FROM cal_unit_price
GROUP BY product_id, quantity
)
SELECT o.product_id, o.discount, o.market, o.region, o.sales, o.quantity, COUNT(c.calculated_quantity) AS calculated_quantity
FROM orders AS o
INNER JOIN cal_quantity AS c
ON o.product_id = c.product_id
WHERE o.quantity IS NULL
GROUP BY o.product_id, o.discount, o.market, o.region, o.sales, o.quantity