Re: DB2OLEDB update attempt

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

Thanks Dan, that does make more sense, I'll send that to the fellow 
doing the SQL server side.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/21/2013 11:35 AM, Dan Kimmel wrote:
> Can you put your where clause within the select statement so you don't pull back the entire table?
>
> Something like
>
> update j set j.qzfy = 14
> from openquery(S10xxxxx, 'select * from patftp.f594063 where qz$wsa=2604378')
>
> > >  
> > >  Folks:
> > >  
> > >  We are trying to have MS SQL server connect to IBM i DB/2 ( V5R4M5 btw )
> > >  to update several ( under 30 ) rows.  We get the following messages, and
> > >  I can't find any references to the SQLSTATE: HY0000.    It takes about
> > >  30 seconds to fail with the following
> > >  
> > >  OLE DB provider "DB2OLEDB" for linked server "S10xxxxx" returned message
> > >  "The maximum number of statements has been reached for the current
> > >  connection. SQLSTATE: HY000, SQLCODE: -1500".
> > >  
> > >  Msg 7320, Level 16, State 2, Line 1
> > >  
> > >  Cannot execute the query "select * from patftp.f594063" against OLE DB
> > >  provider "DB2OLEDB" for linked server "S10xxxxx".
> > >  
> > >  updatej set j.qzfy = 14
> > >  
> > >  from openquery(S1xxxxxx, 'select * from patftp.f594063') j
> > >  
> > >  where j.qz$wsa = 2604378
> > >  
> > >  
> > >  Any ideas?
> > >  
> > >  --
> > >  Jim Oberholtzer
> > >  Chief Technical Architect
> > >  Agile Technology Architects
> > >  
> > >  --