[cchiu]

Thanks a lot for your help. Looks like updating to latest SqlYog did the trick. We're currently importing the database with big smiles.

[cchiu]

peterlaursen wrote on Aug 8 2006, 02:36 PM:

What is the program version that you are using?

v5.02

Quote:

What is the Source database that you are importing from?

It is a Timberline Pervasive SQL database that is used via ODBC.

Quote:

What is the MySQL version that you are importing to?

5.0.22 on CentOS 4.3

Quote:

Is it possible to create a not too big and unambigious 'test case' ? With this error we will only need structure – no data I think? Also try saving the jobfile and attach it here (or create a ticket if you don't want to expose it)

This “”ERROR: 1280, Incorrect index name”” is a MySQL server error – not a SQLyog error. It looks like index names are generated from the column names – and that these column names are not valid with MySQL as index names. Some PK-column for each table? If so try changing the column name from the 'map' button – and avoid using special characters.

Being it is an MySQL error, here is the SQL text it is using to create one of the tables.

Code:

CREATE TABLE `tphp`.`COMPANY_INFORMATION`(
`Company_Name` varchar(33) NOT NULL,
`Company_Address_1` varchar(33) NULL,
`Company_Address_2` varchar(33) NULL,
`Company_City` varchar(15) NULL,
`Company_State` varchar(4) NULL,
`Company_Zip_Code` varchar(10) NULL,
`Company_Phone` varchar(15) NULL,
`Company_Fax` varchar(15) NULL,
`Company_Email` varchar(50) NULL,
`Company_Web_Address` varchar(254) NULL,
PRIMARY KEY (`Company_Name` )
);

For some reason, this worked earlier in the year when we first bought SQLYog, but now the Error 1280 lingers and is poorly documented online and with any useful outputs.

Thanks again for any help you all can provide.

[Author]

Posts