One of the better ways to handle SQL statements (IMHO) is to do all database access through stored procedures; there is no practical limit (follow database guidelines) on the size of any SQL statements within a stored procedure. From the perl side, just make stored procedure calls. -----Original Message----- From: mark warren bracher [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 06, 2001 6:33 PM To: Warden, Ronald MCF:EX Cc: '[EMAIL PROTECTED]' Subject: Re: What is the maximum size of an SQL statement that can be prepared and executed? my recollection from oracle 7 (though at the moment I can't back it up readily with a citation) is that a sql statement (as prepared) had to fit in a varchar2. that's as _prepared_, so bound data wasn't counted. so in o7, that was 2000 characters. I'm not sure if it is 2000 or 4000 in o8; or even if o8 structures the restriction similiarly. - mark Warden, Ronald MCF:EX wrote: > What is the maximum size of a SQL statement that the DBD::ORACLE and DBI can > handle? I have a select statement that is 2183 character long, it fails in > the execute phase. That is to say the prepare works fine, yet the execute > produces and error ( the error is that the SYSTEM table fails on an extend. > Yes, I have add 700 MB more to the SYSTEM table and I still get the error. > The error occurs on the very first pass, even before I try to do a fetch.) > > Thanks for the help. > --- > Ronald Warden > Corporate Data Manager > 250.356.0466 > Data Services Branch > Ministry for Children and Families > ******************************************************** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. All e-mails at Neuberger Berman are, in accordance with Firm policy, to be used for Neuberger Berman business purposes only. E-mails sent from or to the Firm are subject to being reviewed by the Firm in accordance with the Firm's procedure for the review of correspondence.
