|GTswagger||Cannot get InnoDB enabled on my MySQL server.... using a MySQL stock my-huge.cnf ... and uncommenting all innodb lines in the fine.... and making sure "skip-innodb" is not in the file... InnoDB still shows as Disabled in phpmyadmin ... any ideas? :(|
hi. when I try create temporary table if not exists xxx, it fails with "ERROR 1049 (42000): Unknown database mydv". if I remove the "temporary" keyword, it creates the table OK. what can be the problem?
|mishehu||is it safe for me to take my innodb and myisam db files from a 32bit system to an x86_64 system, run a few queries (deletes and alter tables) and then move it back to the 32bit system?|
I'm trying to clean up a dspam database that for some reason did not get cleaned up in a loooong time (more than a year), and the 32bit system can't handle it - it's trashing the drives like mad.
|Mrdini||mishehu, & the x86_64 system would help how? is it significantly faster?|
|mishehu||Mrdini: by all means yes. the 32bit system is a uniproc xeon 3.065GHz from over 2 years ago, and the x86_64 is an opteron 270 (dual core). the 32bit has a raid1, the x86_64 has a raid5...|
|Mrdini||mishehu, well, can't comment on the move, but just wondering thou' - could the tables be indexed badly?|
|mishehu||running a delete type of query has this load -> Cpu(s): 2.0% us, 0.7% sy, 0.0% ni, 0.0% id, 97.3% wa, 0.0% hi, 0.0% si|
I'm not sure really...
the one table I'm operating on right now is a myisam table, the index file is abotu the same size as the data and their is only one index that I can think of.
you think I should do a REPAIR TABLE on it?
|DavidHKMrPowers||is it a good habit to give all tables a index column which is only 1,2,3... ?|
|Mrdini||*shrugs* can't hurt? (by no means an expert in super-big tables)|
|mishehu||DavidHKMrPowers: do you mean an auto_increment?|
|mishehu||DavidHKMrPowers: that depends on your purposes and which engine you're using.|
|mishehu||donno, you tell us what your purposes are.|
we'll be glad to share our opinions.
|DavidHKMrPowers||i want to have an index column because the no. of row can be recorded so that it can be retrived directly next time|
|chadmaynard||DavidHKMrPowers: the real question is "are you going to query by it?" when dealing with indices|
I think you said your index file is just as big as the data file? That means your index is useless
|mishehu||chadmaynard: shrug, I can show you the schema that dspam uses for that table...|
I'm going to try a repair table on it to see if it cleans up the index.
|Xgc||chadmaynard: An ordered index .vs. unordered table has much different behavior, even if the same size.|
|DavidHKMrPowers||so, should I add an index column??|
|chadmaynard||oh. I never knew that. Xgc is once again my hero|
|Xgc||DavidHKMrPowers: If it helps, absolutely.|
|DavidHKMrPowers||Xgc, ok, thanks :D|
|mishehu||DavidHKMrPowers: again, if it is data that you are going to use, or if it's an innodb table (which I *think* adds one for you implicitly even if you don't explicitly specify one... folks can correct me if I'm wrong of course)|
I don't like to add data to a table that I'm not going to use.
|DavidHKMrPowers||mishehu, i am not sure whether i will use this index column :P|
btw, what should be the no. max records in a table?
no. of max