ETL and Data Integration tools - Modern ETL software for everyone

I recently upgraded from 7.7.4.11 to 7.7.5.14. The query works fine in 7.7.4.11 but not in 7.7.5.14.

The query transfers a table from openedge/progress 10.1b sp3 to sql. On a test MS Server 2003 R2 it works fine given the same progress driver, the same progress source and same target sql server but on the important sql server running MS Server 2003 R2 and SQL Server 2005 (which is the actual target sql server referenced in the test server) half the fields come over as Null.

where the first row column is NULL in 7.7.5.14 it makes all the subsequent row's fields in that column NULL whereas in 7.7.4.11 (and the test server running 7.7.5.14) it is fine.

Any ideas? I still can't go live with the upgrade I was hoping to do. You recently sorted out a bulk import issue which initially stopped me from upgrading.

Regards,
Scott

Scott

1. It would be interesting to see the screen shot of mapping with data
Can you see the actual data for [MT-CODE] field or is it always null?

2. Can you set IfError to Reject and run it we might get something useful in the log

Field=MT-CODE
Mapping=Mapped To
MappedTo=[MT-CODE]
Calculated=
Format=
Default=
IfNull=Ignore
IfError=Set To Null <<<<<<< change it to reject
Key=False

Mike

Mike

A
1. It would be interesting to see the screen shot of mapping with data
On screen it shows the data correctly

2. set IfError to Reject
This does not make a difference, no errors occur and the
but the following works
ifNull Set to Default. Where Default = "Any text". Regardless of IfError setting.
and the following does not
ifNull Set to Default. Where Default = "". Regardless of IfError setting.
but the following works
ifNull Set to Reject. Regardless of IfError setting.

B. Possible to run 2 versions of Vis Imp Ent on same server?
Is it possible to run 2 versions of Vis Imp Ent on the same server? The reason is that I have to upgrade/downgrade all the time to provide evidence for you whilst still leaving the production server working correctly.

Scott

Still can't reproduce the problem...

These are my Sql Server odbc drivers what are yours?

Sql Native Client 2005.90.4035.00
SQL Server 6.00.6002.18005
SQL Server Native Client 10.0 2007.100.1600.22

Good news.
SQL Native Client Versions
1. On your system and my working system showed 2005.90.4035.00
2. On my sql server showed 2005.90.3042.00

I have upgraded this driver to .4035 and the imports now work.

FYI In case anyone else has an issue, the update was here
www.microsoft.com/downloads/details.aspx...5&displayLang=en
Feature Pack for Microsoft SQL Server 2005 - December 2008

I keep the server up to date so I don't know why the driver was old?

Thanks for your work on this. Once we found out it wasn't a problem with the Progress driver (because you got me to check and Excel didn't work either) then that pointed at the SQL driver. Once I saw your system and my working one shared the same driver it meant that it was very likely to be a problem with the sql native client driver version.

Scott