Migration or setup script runs CREATE DATABASE without IF NOT EXISTS. CI/CD pipeline runs database setup idempotently but the database was not dropped between runs. The database name already exists from a previous partially completed setup

Step 1: Use CREATE DATABASE IF NOT EXISTS: `CREATE DATABASE IF NOT EXISTS your_db CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;`. Step 2: If you need a fresh database, drop it first: `DROP DATABASE IF EXISTS your_db; CREATE DATABASE your_db;`. Step 3: List existing databases to confirm: `SHOW DATABASES;`

Low severityschema

Power BI Refresh Error:
1007

What does this error mean?

A CREATE DATABASE statement failed because a database with that name already exists.

Common causes

1Migration or setup script runs CREATE DATABASE without IF NOT EXISTS
2CI/CD pipeline runs database setup idempotently but the database was not dropped between runs
3The database name already exists from a previous partially completed setup

How to fix it

1Step 1: Use CREATE DATABASE IF NOT EXISTS: `CREATE DATABASE IF NOT EXISTS your_db CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;`
2Step 2: If you need a fresh database, drop it first: `DROP DATABASE IF EXISTS your_db; CREATE DATABASE your_db;`
3Step 3: List existing databases to confirm: `SHOW DATABASES;`

Frequently asked questions

How do I make CREATE DATABASE idempotent in MySQL?

Use `CREATE DATABASE IF NOT EXISTS your_db;` — MySQL silently skips creation if the database already exists without returning an error.

Can I use IF NOT EXISTS for CREATE SCHEMA as well?

Yes — in MySQL, CREATE SCHEMA is a synonym for CREATE DATABASE. `CREATE SCHEMA IF NOT EXISTS your_schema;` works the same way.

When would MySQL error 1007 block a pipeline?

In ADF Script activities or dbt pre-hooks that create schemas as part of setup — they will fail if the database already exists and IF NOT EXISTS is not used.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html