B
bbrennan
Guest
A customer called with the following situation: OE10.1C on Windows 2008 Server. They run a client server application. They also have some data reporting tool that an end user can work to write SQL queries to the database. For now the name is not important because I do not know it 
In fact, they may run more than one tool. The tool(s) runs native on the the db server. Users being users, they seem to create poorly formed and inefficient queries. Like most tools, there is little to no optimization and they allow the user to cripple a perfectly good machine with a horrible query. I am starting to research how to manage (find, kill, alter state, alter priority, restrict) any such ill-formed queries. Ideally, I need to find a way to identify a query and either remove it or knock it down so as not to bring the production machine to it's knees. Thoughts or shared experiences on the topic? Thanks, Bob Brennan
Continue reading...
In fact, they may run more than one tool. The tool(s) runs native on the the db server. Users being users, they seem to create poorly formed and inefficient queries. Like most tools, there is little to no optimization and they allow the user to cripple a perfectly good machine with a horrible query. I am starting to research how to manage (find, kill, alter state, alter priority, restrict) any such ill-formed queries. Ideally, I need to find a way to identify a query and either remove it or knock it down so as not to bring the production machine to it's knees. Thoughts or shared experiences on the topic? Thanks, Bob BrennanContinue reading...