Malformed query detection
- From: Jonathan Ball <jonball@xxxxxxxxxxxxxx>
- Date: Thu, 29 Jan 2009 12:16:50 -0800
We keep getting SQL statements running through the database server jobs that have cross joins (Cartesian products), i.e. tables with no join specification. These jobs consume enormous amounts of temporary storage building their result sets before we detect them and end the jobs. I know they're doing cross joins because I retrieve the SQL statements via iSeries Navigator and examine them.
Is there a way to configure one of the database server exit points, e.g. QIBM_QZDA_SQL1 or _SQL2, to do some kind of quick analysis of the SQL statement looking for cross joined tables, and reject the statement if found?
.
- Follow-Ups:
- Re: Malformed query detection
- From: Thad Rizzi
- Re: Malformed query detection
- Prev by Date: Re: ArrayList to RpgIle
- Next by Date: NetServer Problem trying to copy libs between machines
- Previous by thread: ArrayList to RpgIle
- Next by thread: Re: Malformed query detection
- Index(es):
Relevant Pages
|