I did some tests with 20GB tables and several millions of rows a few months
back, and what helped improve the performance the most was to separate the
(small) columns used for searching from the (large) columns containing data.
My test table was from a messaging system, and I redesigned it so that
No, no, no, no need to make it that complicated! :-)
If your table has the columns col1, col2, col3, col4, etc, and col1 is the
autoincrement column, and you want to duplicate the entire table, something
like this should work:
INSERT INTO t1(col2, col3, col4, ...)
SELECT col2, col3, col4, ...
be nice if I could get rid of this. I'm
completely stumped. Any ideas?
No, I did not choose the sort order. No, I can not change the values used.
Yes, it has to be this sort order. :-)
/Henrik Schröder
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe
-
From: Victor Pendleton [mailto:[EMAIL PROTECTED]
Sent: den 24 mars 2004 16:22
To: [EMAIL PROTECTED]; Henrik Schröder; '[EMAIL PROTECTED]'
Subject: Re: How to optimize ugly order by?
Let me rephrase my statement. Does the index being used include the order by
columns? If not, the optimizer
Hemert [mailto:[EMAIL PROTECTED]
Sent: den 24 mars 2004 16:12
To: [EMAIL PROTECTED]
Subject: Re: How to optimize ugly order by?
From: Henrik Schröder [EMAIL PROTECTED]
used a lot in various searches, and all results should be ordered by
membership type, but the order should not be 0-1-2
