To delete rows from a table based on data in another table using SQL, use DELETE with JOIN. 1. Use INNER JOIN to delete rows that match in both tables, such as deleting orders for inactive customers. 2. Use LEFT JOIN with a NULL check to delete rows in one table that have no match in the other, like removing users with no orders. 3. For large datasets, delete in batches using LIMIT or TOP to avoid performance issues and reduce lock contention. Always verify affected rows first with SELECT before executing DELETE and ensure join conditions are accurate to prevent accidental deletions.
When you need to delete rows from a table based on data in another table using SQL, joins are your go-to method. The trick is structuring the DELETE statement correctly with a JOIN so that only the intended rows get removed — no more, no less.

Use INNER JOIN to Delete Matching Rows
The most common scenario is deleting rows from one table where there’s a match in another. For example, deleting old orders for a specific customer.

Here’s how to do it:
DELETE o FROM orders o INNER JOIN customers c ON o.customer_id = c.id WHERE c.status = 'inactive';
This deletes all orders from the orders
table where the associated customer in the customers
table has a status of ‘inactive’.
Key points:

- Make sure the JOIN condition accurately reflects what you want to delete.
- Always double-check by running a SELECT first (replace DELETE with SELECT) to confirm which rows will be affected.
Avoid Accidental Deletes with LEFT JOIN and NULL Check
Sometimes you want to delete rows that don’t have a match in another table. That’s where a LEFT JOIN with a NULL check comes in handy.
Say you want to delete users who haven’t placed any orders yet:
DELETE u FROM users u LEFT JOIN orders o ON u.id = o.user_id WHERE o.user_id IS NULL;
What this does:
- Joins the
users
table withorders
on user ID. - Keeps only those users with no matching order (
o.user_id IS NULL
). - Deletes them from the
users
table.
Important: Be careful not to reverse the tables in the LEFT JOIN — that would give you the opposite result.
Handle Large Deletes in Batches
If you're working with large datasets, deleting too many rows at once can lock tables or overload the server.
To avoid issues, delete in smaller batches using LIMIT or TOP, depending on your database:
For MySQL:
DELETE o FROM orders o INNER JOIN customers c ON o.customer_id = c.id WHERE c.status = 'inactive' LIMIT 1000;
Repeat until all needed rows are deleted. You can wrap this in a script or loop if automation is required.
Why this matters:
- Reduces lock contention.
- Lowers the risk of long-running transactions.
- Easier to monitor and control during production use.
That's basically how you handle row deletions using joins in SQL. It’s straightforward once you know which type of join fits your case and how to structure the query safely. Just remember to test with SELECT before DELETE, and consider performance when dealing with big tables.
The above is the detailed content of Deleting Rows Based on Joins in SQL.. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

In database design, use the CREATETABLE statement to define table structures and constraints to ensure data integrity. 1. Each table needs to specify the field, data type and primary key, such as user_idINTPRIMARYKEY; 2. Add NOTNULL, UNIQUE, DEFAULT and other constraints to improve data consistency, such as emailVARCHAR(255)NOTNULLUNIQUE; 3. Use FOREIGNKEY to establish the relationship between tables, such as orders table references the primary key of the users table through user_id.

The main difference between WHERE and HAVING is the filtering timing: 1. WHERE filters rows before grouping, acting on the original data, and cannot use the aggregate function; 2. HAVING filters the results after grouping, and acting on the aggregated data, and can use the aggregate function. For example, when using WHERE to screen high-paying employees in the query, then group statistics, and then use HAVING to screen departments with an average salary of more than 60,000, the order of the two cannot be changed. WHERE always executes first to ensure that only rows that meet the conditions participate in the grouping, and HAVING further filters the final output based on the grouping results.

SQLfunctionsandstoredproceduresdifferinpurpose,returnbehavior,callingcontext,andsecurity.1.Functionsreturnasinglevalueortableandareusedforcomputationswithinqueries,whileproceduresperformcomplexoperationsanddatamodifications.2.Functionsmustreturnavalu

LAG and LEAD in SQL are window functions used to compare the current row with the previous row data. 1. LAG (column, offset, default) is used to obtain the data of the offset line before the current line. The default value is 1. If there is no previous line, the default is returned; 2. LEAD (column, offset, default) is used to obtain the subsequent line. They are often used in time series analysis, such as calculating sales changes, user behavior intervals, etc. For example, obtain the sales of the previous day through LAG (sales, 1, 0) and calculate the difference and growth rate; obtain the next visit time through LEAD (visit_date) and calculate the number of days between them in combination with DATEDIFF;

To find columns with specific names in SQL databases, it can be achieved through system information schema or the database comes with its own metadata table. 1. Use INFORMATION_SCHEMA.COLUMNS query is suitable for most SQL databases, such as MySQL, PostgreSQL and SQLServer, and matches through SELECTTABLE_NAME, COLUMN_NAME and combined with WHERECOLUMN_NAMELIKE or =; 2. Specific databases can query system tables or views, such as SQLServer uses sys.columns to combine sys.tables for JOIN query, PostgreSQL can be used through inf

Pattern matching functions in SQL include LIKE operator and REGEXP regular expression matching. 1. The LIKE operator uses wildcards '%' and '_' to perform pattern matching at basic and specific locations. 2.REGEXP is used for more complex string matching, such as the extraction of email formats and log error messages. Pattern matching is very useful in data analysis and processing, but attention should be paid to query performance issues.

Backing up and restoring SQL databases is a key operation to prevent data loss and system failure. 1. Use SSMS to visually back up the database, select complete and differential backup types and set a secure path; 2. Use T-SQL commands to achieve flexible backups, supporting automation and remote execution; 3. Recovering the database can be completed through SSMS or RESTOREDATABASE commands, and use WITHREPLACE and SINGLE_USER modes if necessary; 4. Pay attention to permission configuration, path access, avoid overwriting the production environment and verifying backup integrity. Mastering these methods can effectively ensure data security and business continuity.

Create a user using the CREATEUSER command, for example, MySQL: CREATEUSER'new_user'@'host'IDENTIFIEDBY'password'; PostgreSQL: CREATEUSERnew_userWITHPASSWORD'password'; 2. Grant permission to use the GRANT command, such as GRANTSELECTONdatabase_name.TO'new_user'@'host'; 3. Revoke permission to use the REVOKE command, such as REVOKEDELETEONdatabase_name.FROM'new_user
