Feature Request: Ability To Stop Queries.

[sonix666]

Hi there,

first of all, compliments for this great tool. I am coming from a Microsoft SQL Server background, and I like this tool because it resembles the great functionality and power that SQL Query Analyzer always gave me.

As with SQL Query Analyzer, I use SQLyog also for analyzing and solving deadlock and blocking situations. I use two connections to simulate a deadlock or blocking problem. Problem with SQLyog however is that it actively waits on the result of a query. This means that when a query blocks on the transaction running in the other connection, the whole application freezes and never responds again (at least in a timely fashion).

I currently solve this by running two seperate instances of SQLyog so that at least one instance is responding and can be used to rollback that transaction. Or I just restart the MySQL service. The latter on is very crude and the first one is somewhat of an annoyance.

Therefore I have two feature requests:

1) Make the queries run asynchronous, so that waiting for the results of a long running query or blocking query, doesn't freeze the application. In essence I want to be able to keep using other connections in SQLyog while in others queries are running.

2) Introduce an ability to stop a running query. This is certainly handy if you want to stop a long running query. Right now I have two options, either wait for the query to finish or by killing SQLyog. Stopping the query would be much nicer.

With these two features in place, in my opinion, this tool is a great replacement for SQL Analyzer.

Thanks in advance.

[Ritesh]

Which version of SQLyog are you using?

Both these features are already implemented in v4.1.

[peterlaursen]

Another “trick” as I wrote in the BLOGS:

Quote:

I few days ago I came across this report in the MySQL bug reporting system:

http://bugs.mysql.com/bug.php?id=12702

well .. it's not really a bug. But I guess we have all experienced that long running query on 'localhost' “kills” everything so that the computer can't be used for anything else. Reason is that the query proces has a priority of “high” or in numerical terms “8”. Normal priority is “6”. Only very critical system tasks have “9” .

There is a simple setting to give a query proces “normal” priority, as described in the bug report. The setting can be set from “MySQL Administrator” .. Startup variables .. Advanced

I have changed my setting!

[Author]

Posts