 |
 |
Archives of the TeradataForum
Message Posted: Fri, 21 Jun 2013 @ 20:40:57 GMT
Subj: | | Re: [3710] Insufficient memory to parse this request, during QueryRewrite phase |
|
From: | | Anomy Anom |
<-- Anonymously Posted: Friday, June 21, 2013 14:38 -->
Seems odd to have this error for a simple INSERT to a table with a few columns. But if the generated SQL is complex (with CASE statements,
CASTs, function calls, etc.) and/or if there are triggers / constraints / Join Indexes defined on the target table, then it can happen.
There is no harm in increasing MaxParseTreeSegs to allow the optimizer to handle more complex SQL.
| |