Tag: Teradata
-
Two key interview questions for SQL developer candidates
Frequently in my career I’ve selected or helped select ETL and reporting professionals who need SQL skills. For some of those opportunities, placement firms returned resumes with interminable, and nearly identical, lists of technical achievements with excruciating unnecessary detail (paraphrasing: “Wrote SELECT statements using GROUP BY”, “Applied both inner and outer joins”). Before interviewing we…
-
More on “Select Failed. [2646] No more spool space”
Also see the previous related post Escaping Teradata Purgatory (Select Failed. [2646] No more spool space) Not too long ago I posted on how to avoid the dreaded “No more spool space” error in Teradata SQL. That post recounted approaches to restructuring SQL queries so that they would avoid being cancelled for using inordinate amounts…
-
Escaping Teradata Purgatory (Select Failed. [2646] No more spool space)
Also see the related post More on “Select Failed. [2646] No more spool space” If you are a SQL developer or data analyst working with Teradata, it is likely you’ve gotten this error message: “Select Failed. [2646] No more spool space”. Roughly speaking, Teradata “spool” is the space DBAs assign to each user account as…