Home›Tutorials›SQL›Pivot and Unpivot

Pivot and Unpivot

All SQL topics
← Dynamic SQLSQL Security Basics →
∙ Topic

Pivot and Unpivot

PIVOT and UNPIVOT are SQL operations used to transform data. PIVOT converts rows into columns, while UNPIVOT converts columns back into rows.

📝Syntax
PIVOT:
SELECT * FROM (
    SELECT column_name, value
    FROM table_name
) AS source
PIVOT (
    AGGREGATE_FUNCTION(value)
    FOR column_name IN (column1, column2)
) AS pivot_table;

UNPIVOT:
SELECT column1, column2
FROM table_name
UNPIVOT (
    value FOR column_name IN (column1, column2)
) AS unpivot_table;
pivot-and-unpivot.sql
📝 Edit Code
👁 Preview
💡 This preview does not execute SQL; it’s for reading/editing the query.
💡What is PIVOT?
  • 1Converts rows into columns.
  • 2Used for summary reports.
  • 3Requires aggregation.
  • 4Common in reporting systems.
💡What is UNPIVOT?
  • 1Converts columns into rows.
  • 2Reverse of PIVOT.
  • 3Useful for normalization.
  • 4Helps in data transformation.
💡How PIVOT Works
  • 1Groups data by category.
  • 2Applies aggregation.
  • 3Transforms rows into columns.
  • 4Improves report readability.
💡How UNPIVOT Works
  • 1Flattens column data.
  • 2Converts columns into row format.
  • 3Useful for normalization.
  • 4Simplifies data processing.
💡Use Cases
  • 1Financial reporting.
  • 2Sales dashboards.
  • 3Data warehousing.
  • 4Business intelligence systems.
💡Advantages
  • 1Improves reporting structure.
  • 2Simplifies data analysis.
  • 3Helps BI tools.
  • 4Better data visualization.
💡Real-world use cases
  • 1Sales report conversion (rows to columns).
  • 2Monthly report dashboards.
  • 3Financial data summaries.
  • 4Analytics reporting systems.
  • 5Data reshaping for BI tools.
  • 6SaaS products use PIVOT and UNPIVOT in SQL in services, dashboards, background jobs, and API workflows.
  • 7ERP and banking systems apply PIVOT and UNPIVOT in SQL with validation, logging, review, and rollback plans.
  • 8E-commerce and healthcare platforms use PIVOT and UNPIVOT in SQL carefully because reliability and data correctness matter.
💡Internal working
  • 1A Sql program first evaluates the surrounding context, then applies the PIVOT and UNPIVOT in SQL rules to the current data.
  • 2The important mental model is input, transformation, result, and failure path.
  • 3In production, the same flow usually sits inside a larger layer such as a controller, service, repository, job, or UI component.
💡Performance considerations
  • 1Choose the simplest implementation first, then measure real workloads.
  • 2Watch for repeated work inside loops, unnecessary allocations, and slow I/O in hot paths.
  • 3Prefer clear data structures and stable APIs before micro-optimizing syntax.
💡Security considerations
  • 1Treat external input as untrusted until it is validated.
  • 2Avoid hardcoded secrets and never print sensitive values in examples or logs.
  • 3Use established libraries for authentication, encryption, parsing, and database access.
💡Common mistakes
  • 1Confusing pivot syntax across databases.
  • 2Using pivot without aggregation.
  • 3Incorrect column mapping in UNPIVOT.
  • 4Ignoring NULL handling.
  • 5Skipping the small working example before adding framework code.
  • 6Ignoring null, empty, duplicate, and boundary inputs.
  • 7Mixing business logic, input handling, and output formatting in one place.
  • 8Using broad error handling that hides the real failure.
  • 9Forgetting to test the behavior after refactoring.
  • 10Adding clever code that future maintainers will struggle to read.
💡Professional best practices
  • 1Use aggregation functions in PIVOT.
  • 2Ensure correct column mapping.
  • 3Handle NULL values properly.
  • 4Use for reporting and analytics only.
  • 5Start with clear requirements and one minimal working example.
  • 6Use meaningful names that explain business intent.
  • 7Keep examples small enough to debug line by line.
  • 8Validate input at every trust boundary.
  • 9Handle errors explicitly and preserve useful context.
  • 10Prefer simple control flow over deeply nested logic.
  • 11Separate domain logic from I/O and framework code.
  • 12Write tests for normal, boundary, and failure cases.
  • 13Review security assumptions before production use.
  • 14Measure performance before optimizing.
  • 15Document non-obvious decisions close to the code or in project notes.
  • 16Use official documentation when behavior is version-specific.
  • 17Keep dependencies current and remove unused code.
  • 18Avoid hardcoded secrets, credentials, and environment-specific paths.
  • 19Log operational events without exposing sensitive data.
  • 20Design examples so learners can safely modify and rerun them.
💡Coding exercises
  • 1Beginner: rewrite the example with different names and values.
  • 2Intermediate: add validation and handle one expected failure case.
  • 3Advanced: place PIVOT and UNPIVOT in SQL inside a small service-style design with tests.
💡Mini project
  • 1Build a small Sql console feature that demonstrates PIVOT and UNPIVOT in SQL.
  • 2Accept input, process it with the concept, print a clear result, and handle invalid input.
  • 3Add a README note explaining the design choice and two edge cases you tested.
💡Troubleshooting
  • 1If the program does not compile, check spelling, imports, braces, and file/class names first.
  • 2If output is unexpected, print intermediate values and verify each branch of the logic.
  • 3If the design feels complex, reduce it to the smallest working example and add pieces back one at a time.
💡Next steps
  • 1Practice PIVOT and UNPIVOT in SQL with a second example from a business domain such as inventory, payroll, banking, or e-commerce.
  • 2Review related Sql topics that cover data flow, error handling, testing, and clean design.
  • 3Compare your solution with official documentation and simplify anything you cannot explain clearly.
🏢Real-world
  • 1Sales report conversion (rows to columns).
  • 2Monthly report dashboards.
  • 3Financial data summaries.
  • 4Analytics reporting systems.
  • 5Data reshaping for BI tools.
  • 6SaaS products use PIVOT and UNPIVOT in SQL in services, dashboards, background jobs, and API workflows.
  • 7ERP and banking systems apply PIVOT and UNPIVOT in SQL with validation, logging, review, and rollback plans.
  • 8E-commerce and healthcare platforms use PIVOT and UNPIVOT in SQL carefully because reliability and data correctness matter.
⚠Common Mistakes
  • 1Confusing pivot syntax across databases.
  • 2Using pivot without aggregation.
  • 3Incorrect column mapping in UNPIVOT.
  • 4Ignoring NULL handling.
  • 5Skipping the small working example before adding framework code.
  • 6Ignoring null, empty, duplicate, and boundary inputs.
  • 7Mixing business logic, input handling, and output formatting in one place.
  • 8Using broad error handling that hides the real failure.
  • 9Forgetting to test the behavior after refactoring.
  • 10Adding clever code that future maintainers will struggle to read.
  • 11Not checking performance on realistic input sizes.
✅Best Practices
  • 1Use aggregation functions in PIVOT.
  • 2Ensure correct column mapping.
  • 3Handle NULL values properly.
  • 4Use for reporting and analytics only.
  • 5Start with clear requirements and one minimal working example.
  • 6Use meaningful names that explain business intent.
  • 7Keep examples small enough to debug line by line.
  • 8Validate input at every trust boundary.
  • 9Handle errors explicitly and preserve useful context.
  • 10Prefer simple control flow over deeply nested logic.
  • 11Separate domain logic from I/O and framework code.
  • 12Write tests for normal, boundary, and failure cases.
  • 13Review security assumptions before production use.
  • 14Measure performance before optimizing.
  • 15Document non-obvious decisions close to the code or in project notes.
  • 16Use official documentation when behavior is version-specific.
  • 17Keep dependencies current and remove unused code.
  • 18Avoid hardcoded secrets, credentials, and environment-specific paths.
  • 19Log operational events without exposing sensitive data.
  • 20Design examples so learners can safely modify and rerun them.
  • 21Prefer maintainability over short-term cleverness.
✅Quick Summary
  • PIVOT converts rows into columns.
  • UNPIVOT converts columns into rows.
  • Used in reporting and analytics.
  • Requires aggregation for PIVOT.
  • Helpful in data transformation tasks.
🎯Interview Questions
Q1. What is PIVOT in SQL?
Answer: A feature that converts rows into columns.
Q2. What is UNPIVOT in SQL?
Answer: A feature that converts columns into rows.
Q3. Where is PIVOT used?
Answer: In reporting and dashboard systems.
Q4. Does PIVOT require aggregation?
Answer: Yes, an aggregate function is required.
Q5. What is the use of UNPIVOT?
Answer: To normalize data by converting columns into rows.
Q6. What is PIVOT and UNPIVOT in SQL?
Answer: PIVOT and UNPIVOT in SQL is a Sql concept used for database-related work. A strong answer explains its purpose, basic behavior, and one realistic use case.
Q7. When should you use PIVOT and UNPIVOT in SQL?
Answer: Use it when it makes the solution clearer, safer, or easier to maintain than a simpler alternative.
Q8. What mistakes should be avoided with PIVOT and UNPIVOT in SQL?
Answer: Querying without indexes or filters. Building commands with untrusted string input.
Q9. How do you debug problems with PIVOT and UNPIVOT in SQL?
Answer: Reduce the code to a minimal example, inspect inputs and outputs, then add logging or tests around the failing path.
Q10. How does PIVOT and UNPIVOT in SQL affect maintainability?
Answer: It improves maintainability when responsibilities are clear, names are meaningful, and edge cases are tested.
Q11. How would you use PIVOT and UNPIVOT in SQL in an enterprise project?
Answer: Place it behind a clear service, validate inputs, handle errors, log useful context, and cover the behavior with tests.
Q12. What performance concern should you check with PIVOT and UNPIVOT in SQL?
Answer: Measure realistic data sizes and look for repeated work, blocking I/O, excessive allocation, or unnecessary framework overhead.
Q13. What security concern should you check with PIVOT and UNPIVOT in SQL?
Answer: Validate untrusted input, avoid leaking sensitive data, and use proven libraries for security-sensitive work.
Q14. How do you explain PIVOT and UNPIVOT in SQL to a beginner?
Answer: Start with the problem it solves, show the smallest working example, then explain each line and one common mistake.
Q15. What should you test for PIVOT and UNPIVOT in SQL?
Answer: Test a normal case, an empty or invalid case, a boundary case, and one expected failure path.
Q16. How do you know if PIVOT and UNPIVOT in SQL is the wrong choice?
Answer: It is probably wrong if it adds complexity without improving clarity, safety, reuse, or performance.
Q17. How does PIVOT and UNPIVOT in SQL connect to clean code?
Answer: Clean code uses the concept with clear names, small scopes, predictable behavior, and minimal hidden side effects.
Q18. What documentation is useful for PIVOT and UNPIVOT in SQL?
Answer: Document assumptions, edge cases, version-specific behavior, and any production decision that is not obvious from the code.
Q19. How should code using PIVOT and UNPIVOT in SQL be reviewed?
Answer: Review correctness first, then readability, failure handling, security boundaries, performance, and tests.
Q20. What is a practical exercise for PIVOT and UNPIVOT in SQL?
Answer: Build a small feature, change the inputs, add one validation rule, and explain the result in your own words.
❓Quiz

What does PIVOT do in SQL?

Related topics

Recursive CTETemporary TablesDynamic SQLSQL Security BasicsDatabase Users and RolesGRANT StatementWhat is SQL?History of SQLFeatures of SQLWhy Learn SQL?
←
PreviousDynamic SQL
SQL Tutorial
NextSQL Security Basics →