I am moving my web server from NT to NetBSD and will need to connect to SQL Server
until I migrate the database to PostgreSQL. I just last night started tinkering with
unixODBC, and found that you need to install some kind of ODBC to ODBC bridge product
on both the Win32 box and the *nix box to access SQL Server databases. Is this
correct? It seems like a monumental kludge. Is this what you are using?
I am using nsodbc on my NT installation of aolserver right now and it works
wonderfully. I don't have any blobs or big text fields, so if the 8k limit applies, I
have not run into it.
Any advice you can give me on setting up access to SQL Server database from a *nix box
would be appreciated...
Ian A. Harding
Programmer/Analyst II
Tacoma-Pierce County Health Department
(253) 798-3549
mailto: [EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 04/26/01 03:11PM >>>
I am curious what folks are doing with nsodbc?
I have been playing around with it on Linux, (in conjunction with the
OpenRDA and Easysoft (unixODBC) Unix ODBC client drivers) connecting to SQL
Server 7 and it works, sort of.
There appears to be a hardcoded limit such that fields cannot be more than
8K in length. That's 8K, not 8G. The field is easily increased raising
the size of a stack allocated buffer, but clearly, nsodbc lacks a basic
strategy on how to deal with even moderately sized fields (much less LOBs
in general.)
So is anyone using this in production? What limitations have you found,
and how have you worked around them?
Also, if you can recommend anyone who had written an nsodbc like driver
before (to create a driver layer into some app connecting to ODBC), please
let me know, I have a client that would be interested in hiring them.
Thanks,
Jerry Asher
=====================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
