| Author |
Topic |
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-19 : 22:30:14
|
| I am exporting data from mssql 2000 to mysql and i am having some problems. I keep getting this error:insert error, column 7 ('column_name')(dbtype_str), status 6, data overflowWhy am i getting this error? what does it mean? The fields that i am migrating are varchar fields, not text/blob fields so i don't expect it to be the myodbc driver, myodbc seems to have a problem migrating text/blob fields. from looking around the net, i should be able to migrate a varchar field.i doubled check to make sure i have plenty of room in mysql for the column varchar(200) just in case...thanks |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-03-20 : 12:05:05
|
| what version of mysql are you using? what version of myodbc? I would make sure you are running the latest release possible. -ec |
 |
|
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-20 : 16:02:54
|
| myodbc v 3.51 & mysql 4.0.18 |
 |
|
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-20 : 16:04:46
|
| i am using the latest myodbc, but the latest version of mysql is 5 something. do you think that could be the problem? |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-03-20 : 22:18:06
|
| don't use version 5, that is alpha release.Actually, the current releaseis 4.1.10a, the 4.0.x release is the last stable release, but it is still being updated. the 3.x release is no longer updated btw.Anyway, I would reccomend that you update your release to atleast 4.0.24. This should actually be relatively easy, you just need to replace the executables with the new ones (no scripts need to be run).btw, this site is SQL Server specific so you probably won't get very good help here on things that are MySQL related. www.dbforums.com has a dedicated support forum for MySQL that might help you out a little more.-ec |
 |
|
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-20 : 22:55:05
|
| Going back to my original question, can you tell me what this error means or the nature of the error? nsert error, column 7 ('column_name')(dbtype_str), status 6, data overflowI will update the db and see what happens after that. |
 |
|
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-20 : 23:01:33
|
| i will check out the other board, but i thought i would give this one a try first since the error is dts generated. |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-03-20 : 23:23:01
|
a quick google search reveals that this is a common error with mysql and SQL Server DTS. Are you using myodbc 3.51.03 or newrer? the readme suggests that this bug was fixed in the 3.51.03 release. btw, 3.51.11 is the latest myodbc for windows. From the myodbc README:quote: -- Fix for errors generated during the export of tables with VARCHAR/TEXT from Access/MS DTS to MySQL using MyODBC. Now driver should be capable of handling all types of conversions.
If you are using the latest myodbc, then you should try using other tools to migrate the data. I have heard that navicat can do this http://www.navicat.com/ as well as the mssql-to-mysql converter here: http://www.convert-in.com/mss2sql.htm.-ec |
 |
|
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-21 : 00:08:11
|
| no, the bug has not been fixed. you can see that here: http://bugs.mysql.com/bug.php?id=996there have been a few other instances of this, but the bug is primarily over text fields. i am not moving blobs, so i shouldn't see the error. do you know what my errors means?i am using dts to take advantage of the scheduling feature. so other tools won't work unless they schedule. |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
|
|
zeronasium
Starting Member
19 Posts |
Posted - 2005-03-21 : 01:58:16
|
| humm, i guess i will have to wait till the next release if i want to do this. just have to find another way... |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-03-21 : 02:02:32
|
quote: Originally posted by zeronasium humm, i guess i will have to wait till the next release if i want to do this. just have to find another way...
You should email the mysql developers to see what the status of this bug is. The only way they are going to work on it, is if they know it is imporatant.-ec |
 |
|
|
|