memory issues for large table query

I'm trying to get a handle on how an increase inf physical memory will affect the query time for a large table. Here's the set up. I'm running MySQL 3.23.37 on RedHat 6.0. The server has a 700Mhz process with 1.5 Gig of RAM. I'm querying a table with 47 million plus records that has 3 columns

show processlist: status

I'm trying to understand what the status field of the SHOW PROCESSLIST command means. When I execute a query - SELECT count(*) as count from table1 where col1 like name%;, the query takes a long time to execute. The table has over 47,000,000 records and is indexed on col1. What does the status

Query optimization

I'm trying to figure out how to optimize a query on a fairly large table. I've been reading the MySQL documentation and have tried a few of the suggestions, but not seem to have much effect on the query. The table contains three columns: 1) int unsigned 2) char(12) 3) char(10) The table has

MySQLGUI file save function

I am using MySQLGUI 1.7.5-1 on Windows 2000. When I save a query result to a file it seems to save it as a Hex output. Is this what is supposed to happen? Can this be used to backup a database? Thanks in advance. Jeff -

Re: MySQLGUI file save function

function Jeff Isom writes: I am using MySQLGUI 1.7.5-1 on Windows 2000. When I save a query result to a file it seems to save it as a Hex output. Is this what is supposed to happen? Can this be used to backup a database? Thanks in advance. Jeff It will save query results in a file

Backing up a MySQL database on a remote server

I'm new to MySQL and I'm sure this has been covered, but I can't find it so I'll ask here. What is the best way to backup a MySQL database that is hosted on a remote server. Our web site is hosted by a hosting company and they configured MySQL. I want to backup the database periodically. I've