Stuck with MySQL workbench query interrupted? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team help a customer deal with this MySQL query.

How to resolve MySQL workbench query interrupted?

Usually, this error will occurs when we are killing long-running queries, either by hand or in an automated fashion.

That is sending a really long SELECT to the server and then to go and administratively kill the query

Today, let us see the methods followed by our Support Techs to resolve it.

• Firstly, if there is no default database selected,just double click on desired one.
• Then, there is a default thousand-row limit in MySQL-Workbench.

The SELECT query will return results but UPDATE or DELETE will fail if the number of records to update exceeds one thousand.

One option is to limit the number of records to update in the query itself or you can adjust the settings.

• Try increasing the timeout values.
• Ensure that KILL QUERY statement causes an error to produce if execution of a statement was really interrupt.

Every place in the server that aborts in case the connection was kill should patch to report ER_QUERY_WAS_INTERRUPTED in case the->killed is set and the query decides to abort.

Note, that the error should set only if there it is not set yet – since we may check for thd->killed in more than one place in execution stack.

An easy way to verify that there is no error in the stack yet is to check thd->net.report_error.

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw how our Support Engineers resolve MySQL workbench query interrupted.