Under pressure from the new resource constraints, we found that it was more efficient to separate subqueries into separate volatile tables with a primary index. Subqueries can improve efficiency by reducing the number of columns and/or rows that your query needs to work with.
![dbschema no more spool space dbschema no more spool space](https://www.funix.org/fr/linux/images/mail/architecture-mail.jpg)
In my earlier post I recommended replacing some joins with subqueries.
![dbschema no more spool space dbschema no more spool space](https://i.etsystatic.com/5488326/r/il/6dc1a1/610552826/il_794xN.610552826_io8t.jpg)
![dbschema no more spool space dbschema no more spool space](https://i.etsystatic.com/26337100/r/il/c457d9/2873179032/il_794xN.2873179032_f4dl.jpg)
Dbschema no more spool space how to#
Not too long ago I posted on how to avoid the dreaded “No more spool space” error in Teradata SQL. Also see the previous related post Escaping Teradata Purgatory (Select Failed.