Archives of the TeradataForum

Message Posted: Wed, 05 Mar 2008 @ 21:17:00 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Thank you Victor for your quick reply.

Actually we could narrow down the issue to the following:

When we check disable Parsing and disable Prepare we can avoid this time frame when something happening within the ODBC. The statement got send right away to the DB System. But now we get the error that the maximum SQL request size of 1MB has exceeded even though the request has only 180KB. Anyway in the ODBC Documentation we found that the Statement of a DML has a max of 64K while a DDL has a max which is different (at least higher).

As long as we are below, everything is fine, as soon as we have more, we get this error. I found a remark from you regarding the 1MB limit in the Forum

www.teradataforum.com/teradata/20040213_213116.htm

There is one funny thing:

If we execute the exact same SQL (we wrapped a create view around the SQL) to create a view on that and then resubmit (of course without the Create View stuff) the SQL which cause the 1MB error it works! As soon as we disconnect and reconnect (without deleting the view) or if we delete (without reconnection) the SQL it's not working anymore the 1MB Limit error will occur again.

Also there is still the fact that it works if whe unchecked the parsing and preparing parameter it just takes much longer, also on BTEQ using CLI we have no problem at all.

Is there somehow a workaround to send bigger SQL Statements to the DB via ODBC? Does ODBC for Unix systems provide this 'feature'. What about install additional tools which could support to extend the Size of a SQL statements maybe an additional 'plug-in' which emulates this?

Any help is highly appreciated.

Thanks and Regards

Joerg

	<Prev	Next>		<<First	<Prev	Next>	Last>>