Re: pgsql ODBC 8.1.200 MSSQL Migration Errors - Mailing list pgsql-odbc

From Daniel Holm
Subject Re: pgsql ODBC 8.1.200 MSSQL Migration Errors
Date
Msg-id 22CFEEFF5C5D60429D6B0572DB26625928F45C@iwsbsrv1.InterWorksok.com
Whole thread Raw
In response to pgsql ODBC 8.1.200 MSSQL Migration Errors  ("Daniel Holm" <Daniel.Holm@interworksinc.com>)
Responses Re: pgsql ODBC 8.1.200 MSSQL Migration Errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-odbc
Is there a max file size, or max # of attachments, I sent 4 .log files
yesterday, it totaled around 200K, and I havent seen the message come
through. Is there a delay on the list?

-----Original Message-----
From: Ludek Finstrle [mailto:luf@pzkagis.cz]
Sent: Wednesday, March 01, 2006 1:59 AM
To: Daniel Holm
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] pgsql ODBC 8.1.200 MSSQL Migration Errors

> I am converting a MS SQL 2000 (SP3) database over to PostgreSQL 8.1
> using the latest ODBC driver (08.01.0200). I am using a DTS package in
> SQL server to copy the data over, but I have a table with a "Text"
> column, and the largest piece of data is 220,843 bytes.
>
> Searching through the list, I saw to uncheck the "Text as LongVarChar"
> option, I tried this, but received the same error for every row over
> 1,278 bytes, strange.

If you uncheck it the Text is VarChar (smaller than LongVarChar).

> I reset "Text as LongVarChar" to true, then bumped up the size of Max
> LongVarChar from 8,190 to 32,000. This actually worked for every row
> over 32,000 bytes, progress!
>
> Next, when I set size of "Max LongVarChar" to 225,000 bytes, I receive
> the same error for rows over around 30,000 bytes, strange again.
>
> If I bump it up further to 230,000 bytes, every row fails with the
> error:
>   Query-based insertion or updating of BLOB values is not supported.
> It also looks like it was unable to allocate proper memory and is
> pulling garbage data from somewhere for every row.
>
> Does anyone have any ideas?

Could you post mylog outputs for this three situations? It would
be better if you try it with max 2 rows (it results in smaller mylog).

Regards,

Luf

pgsql-odbc by date:

Previous
From: george young
Date:
Subject: Re: Access as a front-end or another query builder
Next
From: Tom Lane
Date:
Subject: Re: pgsql ODBC 8.1.200 MSSQL Migration Errors