<p>I bumped into this last week, and it is exactly as you suspect... <strong>your new database does not support InnoDB, which is a requirement of Craft.</strong></p>

<p>I'd suggest discussing the matter with your hosting company. In my case, the hosting company was unable to offer InnoDB support in any form, therefore disqualifying them as a viable hosting option for our new site.</p>

CC BY-SA 3.0
2015-02-02T18:55:57.700Z
Yes, thanks Lindsey, that was indeed the problem. For some reason the InnoDB engine which was supposed to be installed on the server I'm using was not, and I had not thought to check. That has been rectified and the SQL upload works now.
Jack McKenzie
CC BY-SA 3.0
2015-02-04T20:45:25.983Z
Got your own vps or server? Check out your mysql error log and run down this check list. http://dev.mysql.com/doc/refman/5.1/en/error-creating-innodb.html
Derak
CC BY-SA 3.0
2015-02-02T06:23:05.863Z
2015-02-02T06:23:05.863Z
Lindsey D
<p>I am attempting to move the database from my local machine running MySQL 5.5.38 to my webhost running 5.1.70. However when I do so I get the following error on at least two tables. I am using a MySQL export/import process.</p>

<blockquote>
  <p>#1071 - Specified key was too long; max key length is 1000 bytes</p>
</blockquote>

<p>Does anyone have any idea how I might overcome this problem, or what is causing it?</p>

CC BY-SA 3.0
2015-02-02T02:54:47.160Z
After you swapped the database's charset and collation to UTF-8/utf8_unicode_ci, did you nuke all of the tables and re-import them?
Brad Bell
CC BY-SA 3.0
2015-02-02T03:12:34.710Z
Hi Brad - yes I did - well I nuked them first, made the ALTER and then reimported. But I've just discovered now the MySQL server does not have the required InnoDB database engine, and I very strongly suspect that is the problem (I worked this out when I tried to do a clean install of Craft).
Jack McKenzie
CC BY-SA 3.0
2015-02-02T04:54:39.500Z
Ahh... no doubt that's certainly part of the problem, if not the problem.
Brad Bell
<database><error>
Moving to another database: "Specified key was too long"
# Moving to another database: "Specified key was too long"

(Asked by: username_0 on 2015-02-02)

I am attempting to move the database from my local machine running MySQL 5.5.38 to my webhost running 5.1.70. However when I do so I get the following error on at least two tables. I am using a MySQL export/import process.

> #1071 - Specified key was too long; max key length is 1000 bytes

Does anyone have any idea how I might overcome this problem, or what is causing it?

**Tags:** database, error

> **Comments:**
> **username_1**: After you swapped the database's charset and collation to UTF-8/utf8_unicode_ci, did you nuke all of the tables and re-import them?  
> **username_0**: Hi Brad - yes I did - well I nuked them first, made the ALTER and then reimported. But I've just discovered now the MySQL server does not have the required InnoDB database engine, and I very strongly suspect that is the problem (I worked this out when I tried to do a clean install of Craft).  
> **username_1**: Ahh... no doubt that's certainly part of the problem, if not the problem.  

---

## 1 answers

### Answer by username_2 on 2015-02-02. Score: 5 | Accepted answer

I bumped into this last week, and it is exactly as you suspect... **your new database does not support InnoDB, which is a requirement of Craft.**

I'd suggest discussing the matter with your hosting company. In my case, the hosting company was unable to offer InnoDB support in any form, therefore disqualifying them as a viable hosting option for our new site.

> **Comments:**
> **username_0**: Yes, thanks Lindsey, that was indeed the problem. For some reason the InnoDB engine which was supposed to be installed on the server I'm using was not, and I had not thought to check. That has been rectified and the SQL upload works now.  
> **username_3**: Got your own vps or server? Check out your mysql error log and run down this check list. http://dev.mysql.com/doc/refman/5.1/en/error-creating-innodb.html  

---

