Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to migrate from MS-SQL Server on Win2K to MySQL on SuSE 9.0 Pro. I use an ERP program named Unisoft Atlantis (written in Delphi). It natively supports MSSQL, Oracle, DB2 and Interbase. It also supports BDE drivers. I have imported the whole the database from MSSQL to MySQL, I have set the user rigths on the MySQL server, I have installed the ODBC driver on my WinXP Pro workstation. The ODBC driver can test the connection between the wks and the server, and it says its OK. Atlantis has a utility to configure the client. It allows to choose the DB engine to use, the server, auth details etc. The utility can also test the connection to the server. It displays the version of the ODBC (which means that it USES the driver) and the message "Connection OK". No errors! When I start the main program (Atlantis client), it opens its main window, sends something to the net (connecting or authenticating, I guess) and freezes. Under normal conditions (MSSQL) it pops up a login window and after logging in it shows its icons, menus, buttons etc. According to the diagnostics of the ODBC driver and of the program itself, all seem to work ok. What am I doing wrong?
I think there is an option in odbc to turn on sql logging - this creates a logfile with timestamps, soemthing like "C:\sql.log" (not sure of the name of the top of my head) Maybe you can use this to see how far the connection is getting.
Are you sure that you have assigned your user all of the relevant permissions on that database, SELECT, INSERT, UPDATE etc?
Thanks david_ross, I tried sql logging and I think I found something.
I read the sql.log file. It is huge and it has the format shown below.
All the lines end with the statement "return code 0 (SQL_SUCCESS)" except 2 or 3 wich end with "return code 1 (SQL_SUCCESS_WITH_INFO)"
Here are some lines from the log file. This is one of the statements with non 0 error code.
I think this is the problem but I don't know what it means. Maybe the data wasn't imported correctly? I tried many ways to export from MSSQL and import to MySQL. There are many converters from the official MySQL site, some take the db directly from MS and import it directly to My. Others take the db from MS and store it to an sql file (plain text, sql commands) or to
ms-access file etc. I tried them all. Any ideas?
Ordinarily this works fine with the MS SQL Server driver but when "Use Regional Settings" is checked in the MS SQL Server ODBC driver DSN setup dialog everything changes. Once "Use Regional Settings" is checked the ODBC driver returns integer fields using the current regional settings and this generally increases the size of the returned data. For UK machines the simple integer 1234, is returned as "1,234.00". The problem is that when "Use Regional Settings" is checked SQLDescribeCol and SQLColAttribute return the same column-size as they do when this setting is unchecked and so for larger numbers the column-size of 10 will be insufficient to hold the number and you will get "string data right truncated".
I made an experiment and the result is a little strange.
The program is currently using an MSSQL database without ODBC (it has native support for MSSQL). I set it up to connect to the MSSQL server through ODBC and got the same result.
All the diagnostics were ok but the client never connected to the server. What's that supposed to mean? Maybe Atlantis can't use ODBC?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.