prevent high cost queries [message #636158] |
Sat, 18 April 2015 07:03 |
|
uman2631
Messages: 16 Registered: November 2011
|
Junior Member |
|
|
I have some users that are executing ridiculous queries against multiple tables with no join conditions. Things like:
select * from tableA, tableB, tableC, tableD, tableE;
This kills our database performance until we run out of TEMP space, and the DBAs get an alert, and we eventually kill the job.
The DBAs are telling us that there's no way for them to prevent users from running these kinds of queries. Is that right?
Ideally we'd like to prevent any query with a cost > some threshold from even getting started. Is there any way to do this?
If not, is there some other standard practice beyond waiting for TEMP space to fill up to manage these things?
|
|
|
|
|
|
|
Re: prevent high cost queries [message #636215 is a reply to message #636162] |
Mon, 20 April 2015 02:52 |
Roachcoach
Messages: 1576 Registered: May 2010 Location: UK
|
Senior Member |
|
|
BlackSwan wrote on Sat, 18 April 2015 14:55>I have some users that are executing ridiculous queries against multiple tables with no join conditions.
It might be simpler to not have folks who issue such SELECT statements against Production DB.
It is always a challenge to solve procedural problems with a technical solution.
I'm in this camp.
A significant undertaking to provide a non-air tight solution or a swift backhand and a "drop user" or "revoke ..." .....wins every time
|
|
|