[freetds] Setting up FreeTDS to work with ODBC Data Source Administrator on Windows 7

Frediano Ziglio freddy77 at gmail.com
Mon Jul 18 05:53:34 EDT 2016


2016-07-17 20:43 GMT+01:00 Pratik Gandhi <pratik31687 at outlook.com>:
> Hi,
>
>
> I am currently working on a database migration project from MS SQL Server to MySQL and am using the MySQL Workbench 6.3 for it. However, I have ran across a problem in migrating some of the data due to character encoding issues and it has been suggested that using FreeTDS driver (instead of Microsoft's ODBC drivers) could be of help.
>
>
> Now, I have spend past couple of days reading stuff online to try and figure out how I can set up my Windows machine with FreeTDS so that ODBC Data Source Administrator recognizes it, which is what is being used by MySQL Workbench. I have, however, been unable to make any progress and am pretty stuck right now. I have downloaded windows binaries from couple of places, but honestly don't know what to do with them. I have also tried working with CMake, but again no luck there as I absolutely have no prior experience with it.
>
>
> I will really appreciate if anyone can help me here and guide me through the process of making this work.
>
>
>
> Thanks,
>
> Pratik


Actually it's much easier than it seems.

The main page you should look is
http://www.freetds.org/userguide/osissues.htm#WINDOWS.
Actually you can download last 1.0 build from
https://ci.appveyor.com/project/FreeTDS/freetds/build/639. Mainly
choose one compiler version (VS 2008/2010/2015 either 32 or 64 bit)
mostly based on bit and the library you have on your machine to avoid
having to install required library. If you don't have OpenSSL you can
download from http://slproweb.com/products/Win32OpenSSL.html. At this
point copy the tdsodbc.dll file somewhere in the system making sure it
can find OpenSSL libraries and register with "regsvr32 tdsodbc.dll"
(from an administrator command line window).
You'll find the driver in your ODBC Data Source Administrator.
Configuration is not very attractive but the ODBC driver is much
better.
At this point you probably want to set "ClientCharset" to UTF-8 (not
sure you can do graphically) and use Workbench.

Frediano


More information about the FreeTDS mailing list