Spool space issue with Teradata queries

[montubhardwaj]

Hello All,

Hope you all doing good and enjoying summer. Today I wanted to discuss on spool space issue which I am getting while running QlikView application.
I am using teradata queries in the application. User ID which I am using in application is having a spool space of 200 gigs.

I have a QV table say ‘ABC’ which is result of 3 concatenated teradata queries. All the queries are running within spool individually. Query1 itself is taking 110 gigs of spool to run it. So my question is : Is it possible that application is failing because other two queries are taking more than 90 gigs to run ? What is the best possible solution to avoid this (changes in the application design).

ABC:

Query1;

Concatenated

Query2;

Concatenated

  Query3;

Thanks,

Sharma

[phaneendra_kunc]

I dont know whether it is possible in your case or not.

But i would suggest to go with Loop & Reduce by a field value and create seperate QVD's and then do your concatenation.

For example: Create individual QVD's for each TIME PERIOD, and at the end you can concatenate these to a single QVD.

you can automate this and no need of having bunch of SQL statements.

Regrads,

Phani

[montubhardwaj · Accepted solution]

Thanks for your time Phani. I was able to resolve this issue by tweaking the table design in which they were joined.

Regards,

Sharma