import problems from sybase ASE

[dubh]

I'm regularly trying to import several hundred thousand rows of data via an SQL query on a single table in a Sybase ASE server to a MySQL database by the ODBC import wizard.

For most small imports from Sybase this works fine. Brilliantly, in fact. However, for larger imports, particularly on columns where there are naturally a lot of NULLs anyway, partway through the import the columns are written to MySQL as all NULLs, when I know that the source data does no such thing.

Yet, if I import the whole table rather than use a query, the data is reproduced in MySQL faithfully.

Has anyone else experienced this sort of thing?

[benito]

HI

I am using Webyog v3.71 and I am importing not nearly as many records as you are, and I am experiencing the same problem.

When importing data from an ODBC connection, columns that have random NULL values are left “NULL” when in fact, there is data in the fields of the according records.

I am importing from Microsoft SQL Server 2000 into a MYSql 4.11 database.

I have even tried importing the column in question alone AND I tried a completely seperate MYSql database and server , however, I still have the same problem.

I know for a fact the data in the column exists as importing into MS Access via ODBC yeilds the results.

I dont even see the ODBC import feature in SQLYog 4. Please help.

Thank you for your time.

[Ritesh]

Can you send me a dump of your database?

Quote:

I  dont even see the ODBC import feature in SQLYog 4

Our latest version is SQLyog 3.71.

[Shadow]

benito may have considered MAX's public beta as v4, it does not have ODBC import functions, yet. Unfortunately, I can't repeat an import involving thousands of records…

[dubh]

dubh wrote on Jul 5 2004, 02:49 PM:

Yet, if I import the whole table rather than use a query, the data is reproduced in MySQL faithfully.

Or so I thought. See here:

http://www.webyog.com/forums/index.php?act…ct=ST&f=7&t=912

[Author]

Posts