MySQL Error 1050: Table Already Exists (42S01)

MySQL Error 1050 (42S01, ER_TABLE_EXISTS_ERROR) means that the table named in your CREATE TABLE statement already exists in the target database. Check which database your connection is using and inspect the table before changing anything. Dropping it just to make the statement run can permanently delete its data.

This is different from Error 1007, which means the database itself already exists.

The error usually looks like this:

ERROR 1050 (42S01): Table 'orders' already exists

The MySQL 8.4 error reference lists Error 1050 and its SQLSTATE. Use the steps below to determine whether you should reuse the table, change its structure, or create a differently named table.

Why MySQL reports Error 1050

CREATE TABLE creates a table; it does not replace a table with the same name. Error 1050 commonly appears when:

• A setup script or migration runs a second time.
• The table was created earlier by another deployment or by a manual command.
• Your connection selected a different database than you expected, and that database already has a table with this name.
• The table exists, but its current columns or indexes differ from the definition in the script.

Confirm the database and inspect the table

Run these statements in the same MySQL connection that produced the error:

SELECT DATABASE();
SHOW TABLES LIKE 'orders';
SHOW CREATE TABLE `orders`;

SELECT DATABASE() shows the currently selected database. If it is not the intended one, select the correct database or qualify the table name in your statement, for example, shop.orders.

SHOW CREATE TABLE returns the existing definition, including its columns, indexes, and constraints. Compare it with the definition your script expects before deciding what to do. If the table does not appear in the database you expected, check the connection settings and the database-qualified name used by the failing statement.

Choose the fix that matches your intent

Reuse the table that is already there

If the existing table is the intended one and its definition is correct, do not run CREATE TABLE again. Continue using it, or update your setup or migration process so it records that the table has already been created.

Make a create script rerunnable with IF NOT EXISTS

For a simple initialization script, you can use IF NOT EXISTS:

CREATE TABLE IF NOT EXISTS `orders` (
  `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
  `customer_id` BIGINT UNSIGNED NOT NULL,
  `created_at` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`)
);

This prevents Error 1050 when orders already exists. However, MySQL does not check that the existing table has the columns, indexes, or constraints in this statement. It will not bring an older table definition up to date. Inspect it with SHOW CREATE TABLE and compare the result with the schema your application needs.

Change the structure of an existing table

If the table should remain but needs a schema change, use a reviewed ALTER TABLE statement after confirming the current definition. For example, if order_status is absent and belongs in the schema:

ALTER TABLE `orders`
  ADD COLUMN `order_status` VARCHAR(20) NOT NULL DEFAULT 'pending';

Check that the column is actually absent before adding it. For more options, see the MySQL ALTER TABLE guide.

Create a separate table

If the script is meant to create a different table, give it a distinct name and confirm that it is targeting the right database. Do not change the name just to suppress the error if application code or a migration expects the original table.

Replace a disposable table only when that is intentional

DROP TABLE removes the table and its data. Before replacing a table, make a backup, confirm that its contents are disposable or recoverable, and check whether other tables depend on it. See the MySQL DROP TABLE guide for the statement’s effects.

Prevent the error in schema migrations

Treat database migrations as versioned changes and run each migration once. If deployment reruns a migration after a partial failure, first compare the migration history with the actual table definition; do not assume that IF NOT EXISTS proves the table is correct. For repeatable initialization scripts, use IF NOT EXISTS only when silently keeping an existing definition is acceptable.

For the table creation syntax and examples, see the MySQL CREATE TABLE tutorial. Browse more fixes in MySQL error troubleshooting.