RE: Limiting QUSER DASD

["Alan Campin" <Alan.Campin@xxxxxxxxxxxxxxxx>]

I have seen this before. 

 

Users creates a query and does the join wrong and suddenly you have
millions of joins instead of one. 

 

For myself, that is why I never let users run queries directly against
tables. 

 

My preferred way is to create a stored procedure to get the data for
them or at the minimum creates views that have the joins they need
pre-created so they don't do this kind of stuff. 

 

Crystal Enterprises has this built in. 

 

Anyway, my two cents. Anything that is for production should go through
a stored procedure. 

 

Looks like folks might have some ideas on how to prevent run away jobs.