RE: Indexing? (Warning: relative newbie.)

To answer your questions in no particular order, YES you can speed it up with indexing. You might want to first create an index on ( blocksize AND physmessage_id ). Why, you might ask, index on physmessage_id? Because then the db won't have to do a fetch on items from the table since it's in

Anyone using LVM for backing up?

We have a 20 gig db (that includes the MYIs and MYDs and FRMs). We are wondering how long LVM snapshots take.. in that how long might the DB be read-locked? Do we have to read-lock it and flush tables? Are we talking half a second, ten-seconds, 20 minutes? Currently, when we copy the raw files

RE: restoring mysql db doesn't restore user passwords

My theory would be that it's an OLD-PASSWORDS issue. It would seem that you might have used the old_passwords=1 in your original configuration my.cnf but it's not in your new configuration file. -Original Message- From: Adam Williams [mailto:awill...@mdah.state.ms.us] Sent: Monday,

Why can't I kill the query cache?

Also titled, I want this to run slow ALL the time... I have a group of dreadful queries that I have to optimize. Some take 20-30 seconds each -- the first time that I run them. But then they never seem to take that long after the first time (taking less than a second then). If I change the

Simple data, simple query giving me a brain-ache

Ok, I have a select statement which must return the distinct names, sorted by ranking (lowest to highest). Seems absurdly simple, right, and I'm sure it would be... look at this example CREATE TABLE IF NOT EXISTS HowToExample ( Name VARCHAR( 32 ), Ranking INTEGER ) ENGINE=MyISAM;

[Q] FULLTEXT index question

Can one make a composite index with FULLTEXT for one column and standard indexing on another? For instance we have a table CREATE TABLE OurData ( TheText TEXT, TheLanguageID INTEGER ); We have a FULLTEXT index on TheText, but want to be able to do searches on TheText AND

(Q) FullText (UTF8)

We are using MySQL 5.0.22 on CENTOS/redhat linux. The table and database character-sets are all utf8. We have a database supporting numerous languages. Of course, full-text works beautifully with most of the languages. But Chinese and Japanese are giving us problems, and there is NO reason

RE: Query not returning Data

Oh boy.. having the date stored as a varchar in that particular format will be profoundly problematic. You might want to store it -MM-DD or the SQL BETWEEN will mangle the expected return results. Does it work (return a non-empty result-set) when you omit the LIMIT clause? Does it work

RE: MySQL database synchronizing from 2 locations

Replication works with Windows (we do it extensively here at work). And it's definitely one option. But if there are any problems, then without some monitoring mechanism, you'll not be alerted if replication chokes (all that will happen is that updates to the slave will seemingly just stop).

RE: Function in Query has Terrible Impact on Indexes Used

My guess, without seeing your database CREATE TABLE statement for this particular table would be that the DATE_FORMAT returns a string, while the LAST_DAY function returns a date-time. If your TLINE_INV_DATE is a VAR/CHAR then use DATE_FORMAT around the LAST_DAY. If TLINE_INV_DATE is a

RE: migrating 4.0 to 5.0

Here's what we did and still do : Our 4.x tables and databases were/are in Latin-1 and all the 5.x tables are/were in utf8. That means that the entire regiment of items (every column, every table, every database) in the old system (4.1) was latin-1 and all the destination items in 5.x were