Tuesday, March 20, 2012

PROGRESS import of field freezes SQL Server

hi,
I've got a SQL 2005 with an odbc connection to a PROGRESS database. We can
transfer data from the progress to the sql but there is 1 field we can not
transfer. This field, proclaimed by the PROGRESS administration, is a field
wich can contain an empty string or up to 8 characters.
But when we try to do a 'select problemfield, goodfield1,goodfield2 from
pub.table' in the import and export wizard and try to preview this select,
SQL Server freezes for a loooooong time resulting in an error "defined by
component".
We have tried to put the problem field into the select clause, with the
where clause without the where clause... always the same result. The datatyp
e
that we use is a varchar(8) or more but it always freezes.
Does anyone have an idea?
Note: when progress exports to a flat file and we import that flat file,
this works without any problems. So instead of using the odbc connection to
transfer the data overnight, we would like to use flat files and import them
with Integration S. Good solution or not?Ok,
We managed to get the import; but via a flatfile source not with the odbc
connector. Wat went wrong I cant say, it wasn't possible to import the field
s
via a ODBC connection, the flatfime however imported like nothing (although
it where millions of rows)
We have to do a lot of cleansing, the progress software sets a ? in fields
that are not filled in. In this case, implicit conversions to smalldatatime
fails. Now that we have everything in nvarchar, I'm sure SSIS will bring us
where we want.
Thx,
"Philippe" wrote:

> hi,
> I've got a SQL 2005 with an odbc connection to a PROGRESS database. We can
> transfer data from the progress to the sql but there is 1 field we can not
> transfer. This field, proclaimed by the PROGRESS administration, is a fiel
d
> wich can contain an empty string or up to 8 characters.
> But when we try to do a 'select problemfield, goodfield1,goodfield2 from
> pub.table' in the import and export wizard and try to preview this select,
> SQL Server freezes for a loooooong time resulting in an error "defined by
> component".
> We have tried to put the problem field into the select clause, with the
> where clause without the where clause... always the same result. The datat
ype
> that we use is a varchar(8) or more but it always freezes.
> Does anyone have an idea?
> Note: when progress exports to a flat file and we import that flat file,
> this works without any problems. So instead of using the odbc connection t
o
> transfer the data overnight, we would like to use flat files and import th
em
> with Integration S. Good solution or not?

No comments:

Post a Comment