By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,179 Members | 2,192 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,179 IT Pros & Developers. It's quick & easy.

ODBC driver for MySQL does not work properly after version upgrade

P: n/a
Dear MS-SQL-Server-group

maybe my message for MySQL is also for you of interest, since the
MS-SQL-Server and it's binary_checksum function is involved
================================================== ===============

Dear group,

we are dealing with some very specific problems with ODBC, where a
connection from SQL-Server to Mysql works with ODBC-driver 3.51.10.00
and does NOT work with ODBC-driver 3.51.11.00. Maybe someone
experiences similar problems or even has a solution ? Some feedback (to
the group) would be highly appreciated.

We use a Microsoft SQL-Server as Headquarter database and some
Mysql-machines on Redhat as satellite-databases. We use a script to
copy and replicate data between satellite and headquarter. This script
is using simple SQL connecting to Mysql-database using ODBC and
"Openrowset".

In order to copy only new data from sattelites we use the
Binary_Checksum function from Microsoft SQL-Server. This works with the
3.51.10.00 version perfectly but it fails with the 3.51.11.00 version,
where it gives us the message (from MS-SQL-Server) "msg 8481 Error
expanding "*": all columns incomparable, '*' expanded to zero columns".
This message comes only for some but not for all statements using the
binary_checksum.

The only way to fix this is to stick with the "old" version of the
ODBC-driver. Could someone please explain what is going one?

I will post this also in the relevant newsgroup of MS-SQL-Server

Thanks

greetings from Vienna

Uli

Jul 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.