SQL Interview Questions (Flashcards)

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is join types.
• The interviewer asks it because they test whether you understand how relational tables combine.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, INNER JOIN returns only matching rows, LEFT JOIN keeps all rows from the left table, RIGHT JOIN keeps all rows from the right, and FULL JOIN keeps all rows from both with NULLs where there is no match.
• If you want to sound stronger, add a compact example such as: SELECT c.name, o.id FROM customers c LEFT JOIN orders o ON c.id = o.customer_id;.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is confusing unmatched rows, ignoring NULLs, or not explaining when each join is useful.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is data removal and schema operations.
• The interviewer asks it because interviewers want to see whether you can distinguish row-level deletion from structural changes.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, DELETE removes chosen rows and can use WHERE, TRUNCATE removes all rows fast, and DROP removes the entire table definition and its data.
• If you want to sound stronger, add a compact example such as: DELETE FROM employees WHERE status = 'inactive';.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is saying TRUNCATE can always be rolled back everywhere, or mixing up data removal with schema removal.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is row filtering versus group filtering.
• The interviewer asks it because this is a classic question because many beginners mix them up.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, WHERE filters rows before grouping, while HAVING filters grouped results after aggregation.
• If you want to sound stronger, add a compact example such as: SELECT dept, COUNT(*) FROM employees WHERE active = 1 GROUP BY dept HAVING COUNT(*) > 5;.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is using aggregates in WHERE or forgetting execution order.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is relational integrity.
• The interviewer asks it because it checks whether you understand how tables are identified and connected.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, a primary key uniquely identifies a row in its own table, while a foreign key references a primary key in another table to preserve relationships.
• If you want to sound stronger, add a compact example such as: orders.customer_id references customers.id.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is saying foreign keys must always be unique or ignoring referential integrity.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is indexing.
• The interviewer asks it because performance questions are very common in SQL interviews.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, an index is a data structure that speeds up reads on columns used in WHERE, JOIN, ORDER BY, or GROUP BY, but it adds overhead for inserts and updates.
• If you want to sound stronger, add a compact example such as: CREATE INDEX idx_orders_customer_id ON orders(customer_id);.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is claiming indexes always make queries faster or ignoring write costs.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is database design.
• The interviewer asks it because interviewers use it to test design thinking, not just query writing.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, normalization organizes data into related tables to reduce duplication and update anomalies, often discussed as 1NF, 2NF, and 3NF.
• If you want to sound stronger, add a compact example such as: splitting customer data from order data instead of repeating customer fields on every order row.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is describing normalization as a rule to create as many tables as possible.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is query structure.
• The interviewer asks it because modern SQL interviews often compare readability and reuse.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, a subquery is nested inside another query, while a common table expression gives a temporary named result set that can improve readability and sometimes recursion support.
• If you want to sound stronger, add a compact example such as: WITH high_spenders AS (SELECT customer_id, SUM(total) amt FROM orders GROUP BY customer_id) SELECT * FROM high_spenders WHERE amt > 1000;.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is saying CTEs are always faster or not explaining maintainability.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is aggregation.
• The interviewer asks it because it is one of the most searched beginner-to-intermediate SQL topics.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, GROUP BY collects rows that share the same value so functions like COUNT, SUM, AVG, MIN, and MAX can be computed per group.
• If you want to sound stronger, add a compact example such as: SELECT dept, AVG(salary) FROM employees GROUP BY dept;.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is selecting non-grouped columns without aggregation and expecting deterministic results.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is analytic queries.
• The interviewer asks it because many modern interviews use them to separate basic candidates from stronger ones.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, window functions calculate values across a related set of rows without collapsing them, such as ROW_NUMBER, RANK, SUM OVER, or LAG.
• If you want to sound stronger, add a compact example such as: SELECT employee_id, salary, RANK() OVER(PARTITION BY dept ORDER BY salary DESC) rnk FROM employees;.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is confusing them with GROUP BY, which reduces row count.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.

Core idea

• This is one of the most common SQL interview questions because it tests whether you understand the concept, can explain it clearly, and know why it matters in real work.
• The core idea is data quality query.
• The interviewer asks it because this appears often in practical SQL interviews.
• A strong answer should begin with a plain-language definition, then move quickly into practical impact.
• For example, you usually group by the suspected duplicate columns and keep groups with COUNT(*) > 1, then join back if you need full rows.
• If you want to sound stronger, add a compact example such as: SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1;.
• You do not need to recite code perfectly, but you should be able to explain what it does and when you would choose that approach in production.
• The best answers also mention trade-offs.
• In SQL and SQL Server, that often means performance versus correctness, readability versus control, or concurrency versus consistency.
• In JavaScript and Selenium, it often means convenience versus runtime behavior, stability, or maintainability.
• This is where stronger candidates stand out: they do not stop at the definition.
• They explain consequences, common failure modes, and one good rule of thumb.
• For example, they may mention how the concept affects query speed, locking, browser flakiness, debugging, or unexpected runtime results.
• A common mistake is grouping by the primary key, which prevents duplicates from appearing.
• Another weak answer is a textbook explanation with no scenario, because interviewers then cannot tell whether the knowledge is usable.
• A better pattern is: define it, compare it to the closest related concept, show a realistic example, mention one trade-off, and finish with a practical takeaway.
• That style works well both in interviews and for search visibility because readers usually want an answer that is accurate, memorable, and immediately applicable.