SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-26-2008, 03:58 PM
| ||||
| ||||
 User Contingency in DB2 UDB 7.2? Is there a way or a workaround to introduce user contingency in DB2 UDB EEE V.7.2? We have a large number of users, some of them are SQL newbies which can execute any kind of SQL statements. It happens often that a single SQL statement takes away all the computing resource (CPU, Memory) and clogs up a powerfull machine, so that none of other simultaneously runing statements can get enough resource to be finished. My question: how can we find a way or exploit some other mechanisms in order to restrict the resource usage by a SQL statement/or a user, so that any statement, regardless small or big, gets a same resource contingency and those killer statements which demand huge resource have to wait or to be killed if their resource contingency is over. Any help will be appriciated! -- Posted via http://dbforums.com      |
|
02-26-2008, 03:58 PM
| ||||
| ||||
| Re: User Contingency in DB2 UDB 7.2? 2 ways: 1. use the governor (db2gov) 2. have a look at Query Patroller (btw, QP is much improved in v8) noname_1234 wrote: > Is there a way or a workaround to introduce user contingency in DB2 UDB > EEE V.7.2? > > > > We have a large number of users, some of them are SQL newbies which can > execute any kind of SQL statements. > > > > It happens often that a single SQL statement takes away all the > computing resource (CPU, Memory) and clogs up a powerfull machine, so > that none of other simultaneously runing statements can get enough > resource to be finished. > > > > My question: how can we find a way or exploit some other mechanisms in > order to restrict the resource usage by a SQL statement/or a user, so > that any statement, regardless small or big, gets a same resource > contingency and those killer statements which demand huge resource have > to wait or to be killed if their resource contingency is over. > > > > Any help will be appriciated! > > > -- > Posted via http://dbforums.com |
 |
« SQL0632N. Why can't a child table be related to multiple parents on multiple FK columns with the on delete set null option?
|
JDBC, DB/2, Apache and TomCat »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 07:46 AM.
