Re: NVARCHAR Columns Dropped from Query Result
Frediano Ziglio <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
You should send us a odbc trace with simple query and security stuff removed. 0.91 support nvarchar much better than 0.64 (it can use wide encoding directly without losing characters). You can also try to use a single character encoding like iso8859-1, this could help to solve some problems with some client that does not like no_total reply. Frediano Ziglio On 19/gen/2012, at 02:05, Jason Lincoln <[email protected]> wrote: > It appears the problem is with Oracle heterogenous database connectivity and not with unixODBC or FreeTDS. I'm still at a bit of a loss as to why it was working flawlessly before the SP3 patch with FreeTDS 0.64. > > On Jan 16, 2012, at 3:48 PM, Jason Lincoln wrote: > >> My freetds/unixODBC Oracle XE Heterogenous database connectivity setup was working great until SP3 came along recently. I was unable to connect until I upgraded to the latest freetds version (0.91) using tdsver=7.1. Now I am able to connect to SQL Server from Oracle using unixODBC/freeTDS but columns are dropped. Seriously. I can run a query in SQL Developer on Windows with a connection to the SQL Server DB and get all the columns in the table but when I run the same query (select * from ...@mssql) from an Oracle DB it drops all nvarchar columns. >> >> Anyone have any suggestions? >> >> Thanks, >> Jason