Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering phpMyAdmin 3.4 for Effective MySQL Management

You're reading from   Mastering phpMyAdmin 3.4 for Effective MySQL Management A complete guide to getting started with phpMyAdmin 3.4 and mastering its features book and ebook

Arrow left icon
Product type Paperback
Published in Feb 2012
Publisher Packt
ISBN-13 9781849517782
Length 394 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (27) Chapters Close

Mastering phpMyAdmin 3.4 for Effective MySQL Management
Credits
About the Author
About the Reviewers
www.PacktPub.com
1. Preface
1. Getting Started with phpMyAdmin FREE CHAPTER 2. Configuring Authentication and Security 3. Over Viewing the Interface 4. Creating and Browsing Tables 5. Changing Data and Structure 6. Exporting Structure and Data (Backup) 7. Importing Structure and Data 8. Searching Data 9. Performing Table and Database Operations 10. Benefiting from the Relational System 11. Entering SQL Statements 12. Generating Multi-table Queries 13. Synchronizing Data and Supporting Replication 14. Using Query Bookmarks 15. Documenting the System 16. Transforming Data using MIME 17. Supporting Features Added in MySQL 5 18. Tracking Changes 19. Administrating the MySQL Server Troubleshooting and Support Index

Stopping an errant query


Suppose we launch a complex search and notice that the browser is waiting for the results. This might happen with a database search but also with a single-table search. We can instruct the browser to stop but this will only tell the web server to cease handling our request. However, at this point the MySQL server process is busy, possibly doing a complex join or a full table scan. Here is a method to stop this errant query:

  1. We open a different browser (for example, the errant query was launched via Firefox and we open Internet Explorer).

  2. We log in via phpMyAdmin to MySQL with the same account.

  3. On the home page, we click on Processes.

  4. At this point, we should see a process identified by Query under the Command column and containing the errant query (other than SHOW PROCESSLIST which is not the one to kill).

  5. We click on Kill for this process.

  6. To verify, we can immediately click again on Processes and the chosen process should now be identified as Killed instead of Query...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image