Re: SQL server connect to DB2 via ODBC problem

ODBC, by definition, receives record sets in "chunks". 30 is probably 
about the number that is left over in the last chunk. Check the SQL server 
logs and you'll probably see a timeout receiving the dataset on the last 
chunk. There's a nasty error returned to the ODBC caller when this 
happens, but your windows side seems to be ignoring it. Next, you'll have 
to see which side is producing the timeout. Window side may be running out 
of memory as most will try to read the whole thing into a memory buffer.




Vernon Hamberg <vhamberg@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/13/2006 06:19 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: SQL server connect to DB2 via ODBC problem






I haven't run into this - but it seems that facts might not matter to 
this consultant - I see 3 components here - one that connects to the 
iSeries (the 3rd component) and gets the right results, and a second 
that connects to the iSeries and gets erroneous results. DOH! what is 
different here? Windows weinies tend to blame anything but their 
stuff, and the iSeries always gets blamed first. Funny thing - it is 
almost never the problem. Trouble is, standard problem analytical 
techniques do not enter this fray.

Rant is over!!

There might be some capacity issues in SQL Server - I suggest some 
kind of search on google for "capacities" or "capabilities" and "SQL 
server" and "link server".

HTH
Vern

At 12:51 PM 9/13/2006, you wrote:

I am working with a client who has some apps that run in Solomon and FRX 

for

reporting.  We are current moving a file, nightly via the QNTC file 

system.

This has been working perfectly for quite a while, but the Solomon
consultants want to retrieve the data directly out of the AS400 database
using ODBC.

One of them said "I have always had a problem with the AS400 via ODBC". 

We

proceeded to set up a test to read a PF that contained about 250000 

records.

He configured SQL server to use a link server, set up the data source and 

we

started to issue SQL statements using the query analyzer.

The statement SELECT * FROM system.library.file retrieved the wrong 

number

of rows/records.  (about 30 less).  The statement SELECT COUNT(*) FROM
system.library.file retrieves the correct count.  When we tried to access
the data using Access rather than SQL server, the correct number of
records/rows are returned.

I say the problem is with SQL server. The Solomon consultant says the
problem is the iSeries.  Anyone ever run into this before?  Any 

suggestions?

Thanks,
Carl

Carl J. Galgano
EDI Consulting Services, Inc.
770-422-2995
www.ediconsulting.com

600 Kennesaw Avenue
Suite 400
Marietta, GA  30060


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.