Archives of the TeradataForum
Message Posted: Thu, 07 Aug 2008 @ 09:21:05 GMT
Joerg, let's not get confused about this again!
For those who did not follow the previous thread on SQL request size limit, here is the reference:
My understanding is:
1. Teradata has the limit of 1 MB on SQL request text (the size in bytes of the SQL statement; not the sum of letters used to specify columns but all the characters together whether they are in columns, table names or predicates; if Unicode strings are used, they will be "expensive");
2. Teradata has the limit of 2 MB on the "expanded" SQL requests for things like views and macros.
3. In theory, these two limits (and no lower limits) should apply regardless of the method we use to send requests to Teradata: native via BTEQ, ODBC or JDBC.
4. In reality, things can get messy as Joerg's thread has shown us: large SQL statements may take a long time to get parsed by ODBC drivers. When we try to disable the ODBC parsing unexpected lower limits on SQL size may all of a sudden be applied by Teradata. They may be caused by the reasons explained in the documentation (and mentioned in the thread above) or simply by bugs.
Is this really the case now? Have they fixed the bug?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|