Re: SQL with no output

| Since the amount of data returned by the queries could be surprisingly
| large, spooling would produce unnecesary junk files and could impact
| elapsed time.

|

so? the 'junk' files will be overwritten by each execution -- and you can have your test script delete them

since your selecting the same rows ('executing the same SQLs after having made changes to the schema or init parameters) the overhead of spooling will be constant -- and aren't you eventually going to actually return data once you move from test to production?

sounds like it's time for the nike approach ('just do it!') ;-)

• mcs