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 product_sales AS (
SELECT
pr.category,
pr.product_name,
ROUND(SUM(o.sales)::numeric, 2) AS product_total_sales,
ROUND(SUM(o.profit)::numeric, 2) AS product_total_profit
FROM orders o
JOIN products pr ON o.product_id = pr.product_id
GROUP BY pr.category, pr.product_name
),
ranked_products AS (
SELECT *,
RANK() OVER (
PARTITION BY category
ORDER BY product_total_sales DESC
) AS product_rank
FROM product_sales
)
SELECT
category,
product_name,
product_total_sales,
product_total_profit,
product_rank
FROM ranked_products
WHERE product_rank <= 5
ORDER BY category ASC, product_rank ASC;-- impute_missing_values
WITH unit_prices AS (
SELECT
product_id,
discount,
market,
region,
AVG(sales / NULLIF(quantity, 0)) AS avg_unit_price
FROM orders
WHERE quantity IS NOT NULL
GROUP BY product_id, discount, market, region
),
enriched_orders AS (
SELECT
o.product_id,
o.discount,
o.market,
o.region,
o.sales,
o.quantity,
ROUND(CASE
WHEN o.quantity IS NULL AND up.avg_unit_price IS NOT NULL THEN o.sales / up.avg_unit_price
ELSE NULL
END) AS calculated_quantity
FROM orders o
LEFT JOIN unit_prices up
ON o.product_id = up.product_id
AND o.discount = up.discount
AND o.market = up.market
AND o.region = up.region
)
SELECT
product_id,
discount,
market,
region,
sales,
quantity,
calculated_quantity
FROM enriched_orders
WHERE quantity IS NULL;