Re: pgsql ODBC 8.1.200 MSSQL Migration Errors

Trying this again, with the attachments zipped up.

Row1: 80804 bytes
Row2: 63456 bytes

Attached are the results for the following 4 runs:

mylog_4172.log
Unknown Sizes: Maximum
Text as LongVarChar: Yes
Max LongVarChar: 225000
MSSQL Error: Data for source column 1 ('textfield') is too large for the
specified buffer size.

mylog_3988.log
Unknown Sizes: Maximum
Text as LongVarChar: Yes
Max LongVarChar: 230000
MSSQL Error: Query-based insertion or updating of BLOB values is not
supported.

mylog_3988_2.log
Unknown Sizes: Maximum
Text as LongVarChar: Yes
Max LongVarChar: 64000
MSSQL Error: Query-based insertion or updating of BLOB values is not
supported.

mylog_5968.log
Unknown Sizes: Maximum
Text as LongVarChar: Yes
Max LongVarChar: 32000
MSSQL Error: Data for source column 1 ('textfield') is too large for the
specified buffer size.

I tried with 64,000, but it came back with the BLOB error... so bizarre.

Thanks for your help!

-Daniel
-----Original Message-----
From: Ludek Finstrle [mailto:luf@pzkagis.cz]
Sent: Wednesday, March 01, 2006 1:59 AM

> 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