metricsign
Start free
Medium severityschema

Power BI Refresh Error:
1075

What does this error mean?

A CREATE TABLE or ALTER TABLE defines more than one AUTO_INCREMENT column, which MySQL does not allow.

Common causes

  • 1ORM or code generator produces a table definition with multiple AUTO_INCREMENT columns
  • 2Copying DDL from another database that allows multiple auto-increment columns (like some versions of MariaDB with sequences)
  • 3Manually adding AUTO_INCREMENT to a second column without removing it from the first

How to fix it

  1. 1Step 1: Identify which columns have AUTO_INCREMENT: `SHOW CREATE TABLE your_table;`
  2. 2Step 2: Remove AUTO_INCREMENT from all but the primary key column: `ALTER TABLE your_table MODIFY COLUMN secondary_col INT NOT NULL;`
  3. 3Step 3: If a second auto-increment column is needed, use a trigger to populate it instead.

Frequently asked questions

Can a MySQL table have multiple auto-incrementing columns?

No — MySQL allows only one AUTO_INCREMENT column per table, and it must be indexed (typically the PRIMARY KEY). Use triggers or application-level logic for additional sequential columns.

Does this restriction apply to MariaDB as well?

MariaDB also restricts AUTO_INCREMENT to one column per table, but MariaDB supports sequences (CREATE SEQUENCE) as an alternative for multiple auto-incrementing values.

How can this error appear in a dbt migration?

If a dbt seed file generates CREATE TABLE DDL from a tool that exports AUTO_INCREMENT on multiple columns, the dbt run will fail with this error on MySQL.

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

Other schema errors