This tutorial demonstrates how to run SQL queries in phpMyAdmin.
SQL queries are commands that you issue to the MySQL server to tell it to perform various functions. Designed for advanced users, this allows you to quickly make changes to your database simply by issuing the appropriate commands.
This tutorial shows you where to execute SQL queries, but not what queries to execute. The exact SQL queries you will execute will depend on what you want to do.
Be careful when executing SQL queries, because it will do whatever you tell it to do (and not necessarily what you want it to do). Always double check any destructive commands (such as DROP) to make sure it is acting upon the items you intend it to act upon. If you are making significant changes, it is recommended that you make a backup before you begin.
Queries are Context Sensitive
The SQL tab appears above all pages inside of phpMyAdmin. This tab is context sensitive, which means that depending on what you're looking at, the target of your SQL queries might be different.
If you are on the home page of phpMyAdmin and do not have any databases selected, if you click the SQL tab, any queries you run will apply to the hosting account.
If you select a database, any queries run by clicking on the SQL tab will apply to that database.
If you select a table within a database, any queries run by clicking on the SQL tab will apply to that table.
Summary of Steps
Begin by accessing phpMyAdmin via cPanel.
Navigate to the area your SQL query will apply to.
The phpMyAdmin home page if you want the query to apply to the entire hosting account.
The database you want to run queries against.
The table you want to run queries against.
Click the SQL tab.
Type in your SQL query.
Click the Go to execute the query.
Your SQL query will be executed and the actions you requested will be performed.
Optimizing MySQL: Queries and Indexes Article 4 of 4 Courtesy of:Ian Gilfillan Most systems need to be highly optimized for selects - take a news site which performs millions of queries per day, but w
Optimizing MySQL: Queries and Indexes Article 1 of 4 Courtesy of: Ian Gilfillan Badly defined or non-existent indexes are one of the primary reasons for poor performance, understanding and then fixing
Optimizing MySQL: Queries and Indexes Article 2 of 4 Courtesy of: Ian Gilfillan Some knowledge of how indexes work allows you to use them more efficiently. Firstly, note that when you update a table w
Optimizing MySQL: Queries and Indexes Article 3 of 4 Courtesy of: Ian Gilfillan Ordering by surname is a common requirement, so it would make sense to create an index on surname. But in this example o