RE: Editing fields in bulk
I could use the same thing... just looking through the documentation there is a replace() function. Maybe do a backup/restore to a test database before doing this on your live system... UPDATE `tablename` SET `fieldname`=REPLACE(tablename.fieldname,'US- Complete','US Complete') WHERE `fieldname` LIKE '%US- Complete%'; -Original Message- From: Brian Dunning [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 September 2007 10:42 AM To: mysql@lists.mysql.com Subject: Editing fields in bulk I have a column where I need to replace all instances of the text "US- Complete" (contained within a long sentence) with "US Complete". There are probably 50 or 100 of them. I'm really scared to do it since I can't risk screwing up that column - what's the correct syntax? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.5/989 - Release Date: 4/09/2007 5:54 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.5/989 - Release Date: 4/09/2007 5:54 PM -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqldump of huge innodb database
Hiya, I was backing up a 95GB InnoDB database and forever had problems. It ended up working and I never really worked out exactly what the cause was... but try using the following: --opt (does --quick + extended-insert + others) --net_buffer_length=1G (set this to whatever you want, 1G is the largest it will support. I was backing up uncompressed audio so had it at 1G. When --opt is set it also uses --extended-insert, the net_buffer_length tells mysqldump when to break the extended insert and create a new insert. Useful when dealing with large packets) --max_allowed_packet=1G (or whatever you expect your largest packet to be, in my case was up to 1G) Example: mysqldump -u mysqldump --password= --opt --verbose --net_buffer_length=1G --max_allowed_packet=1G --single-transaction dbname > dbname.sql If this still fails... try running the backup from a remote computer either by using MySQL Administrator or mysqldump. Occasionally I would get the same error you received when running mysqldump on localhost, however it would complete when run from either my workstation or on another server. I can't really explain why this would happen, but now I just run all of my backups straight to a mirrored server. Example: mysqldump -h 192.168.x.x -u mysqldump --password= --opt --verbose --net_buffer_length=1G --max_allowed_packet=1G --single-transaction dbname > dbname.sql Good luck, hope this helps. Hartz. -Original Message- From: Benjamin Schmidt [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 September 2007 7:05 PM To: mysql@lists.mysql.com Subject: mysqldump of huge innodb database Hello list members Since a few days I get this error message when making a backup of my database: mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `dbmail_messageblks` at row: 174955 Script ended at: Tue Sep 4 06:45:37 CEST 2007 (111137) Execution Time: Hours: 4 Minutes: 282 Seconds: 16956 The ibdata1 file now has a size of 42GB (I use the innodb engine). The command to backup is following: ssh [EMAIL PROTECTED] \ "mysqldump -u mysqldump --password= --quick --single-transaction dbmail | /bin/gzip" > /Backup/mysqldump.tar.gz And this is my config-file (default values from the debian package): ... innodb_data_file_path=ibdata1:10M:autoextend:max:183G key_buffer = 16MB max_allowed_packet = 64M thread_stack = 128K query_cache_limit = 1048576 query_cache_size = 16777216 query_cache_type = 1 set-variable = max_connections=1000 max_allowed_packet = 64M ... As I wrote above, it worked this way a very long time. And it should work again ;) Does anyone know this problem or has an idea? Many thanks in advance, Benjamin Schmidt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.3/986 - Release Date: 3/09/2007 9:31 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.3/986 - Release Date: 3/09/2007 9:31 AM -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Got a packet bigger than 'max_allowed_packet' -> why is mysql so unkind?
Hi Gerald, I have set the max_allowed_packet to 1G on both servers. Any other ideas by any chance? Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! On 01/08/2007, at 11:09 PM, Gerald L. Clark wrote: You must also set max_allowed_packed for the new server, not just the new client.
Got a packet bigger than 'max_allowed_packet' -> why is mysql so unkind?
Hi Everyone, I have had similar problems in the past, and have managed to usually stumble my way around them. But now this officially is just not making any sense... to me at least ;) Problem: I want to backup a database from server1 and restore it to server2. The database size is ~10GB, largest row at any time is ~100M. Here is what I have been doing... Creating the SQL backup # mysqldump --host=192.168.1.61 --user=hburton -p --opt -- single_transaction --verbose --max_allowed_packet=100M -- net_buffer_length=100M mraentertainment > mraentertainment.sql From my understanding, net_buffer_length should tell mysqldump the maximum size that extended-insert rows are allowed to be before beginning a new INSERT row set. I have however tried --skip-extended- insert & --extended-insert=FALSE (believing that the max_allowed_packet that is erring is actually multiple rows in a single INSERT) The backup completes successfully and I have myself a 9.2GB SQL dump file ready to go. Reloading the SQL backup # mysql --host=localhost --user=hburton -p --max_allowed_packet=100M mraentertainment < mraentertainment.sql Error: when trying to load the SQL file into the empty database on the new server I receive the message "ERROR 1153 (08S01) at line 92: Got a packet bigger than 'max_allowed_packet' bytes". I see so many people on forums everywhere that get the same issue... but can not seem to find an answer for this. As you can see, max_allowed_packet for mysqldump (backup) and mysql (restore) are the same. I have also set max_allowed_packet=1G in the config files for MySQL on both servers. I have tried using values up to 1G, as this is apparently the largest value supported according to the documentation. If anyone can help me out with this the assistance is greatly appreciated. Regards, Hartleigh Burton Resident Geek.
Re: MySQL database move
backup and restore would be what i would do. using either mysql administrator or mysqldump. On 09/07/2007, at 3:45 PM, Ace wrote: Hi, We have crisis. Disk with MySQL database is full. Now we want to move database to another disk. How can we do it? -- Thanks, Rajan Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
Hi Dusan, You replied to a forum post of mine on mysql.com yeah? ;) I have tried adjusting the max_allowed_packet on both the server and client. Both are set to 1G now (apparently the highest value accepted) even though each row is no larger than 100M at very most. I am thinking this may have something to do with --extended-insert. So rather than having all of data in an extended insert I have tried disabling this feature with --extended-insert=0, --extended- insert=false, --skip-extended-insert (not all at once obviously)... am I doing this correctly? Mixed results when I search google for answers. I don't really care at this stage if backup/restore times are reduced with this feature disabled, as long as I can get an accurate backup. I also set --net_buffer_length=800M; in theory --extended-insert will only create queries up to this value, so if I keep it lower than the --max_allowed_packet value it should all be sweet. Still no cigar unfortunately. On 19/06/2007, at 7:08 PM, DuĊĦan Pavlica wrote: Try to look for Lost connection error in MySQL manual and it can give your some hints like http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html Dusan Hartleigh Burton napsal(a): Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator & mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. If anyone can help me out with this problem the assistance is greatly appreciated. I have scoured google and various other sources and not found much information that has been useful to me. I hope I have enough info below... if more is required let me know. mysqldump example P:\>mysqldump -u username -p mraentertainment > mraentertainment.sql --opt --verbose --max_allowed_packet=500M --hex-blob --single_transaction --net_buffer_length=100M Enter password: ** -- Connecting to localhost... -- Retrieving table structure for table albums... -- Sending SELECT query... ... -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 my.ini configuration file [client] port=3306 [mysql] default-character-set=latin1 [mysqld] log-bin=itd002-bin server-id=1 port=3306 wait_timeout=86400 max_allowed_packet=100M basedir="C:/Program Files/MySQL/MySQL Server 5.0/" datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/" default-character-set=latin1 default-storage-engine=INNODB sql- mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" max_connections=100 query_cache_size=0 table_cache=256 tmp_table_size=77M thread_cache_size=8 #*** MyISAM Specific options myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G myisam_sort_buffer_size=154M key_buffer_size=130M read_buffer_size=64K read_rnd_buffer_size=256K sort_buffer_size=256K #skip-innodb innodb_additional_mem_pool_size=6M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=3M innodb_buffer_pool_size=252M innodb_log_file_size=126M innodb_thread_concurrency=8 Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
Ok... this error has just started popping up in my .err log file... 070618 14:31:10 InnoDB: ERROR: the age of the last checkpoint is 237821842, InnoDB: which exceeds the log group capacity 237813351. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of log files at least 10 times bigger than the InnoDB: largest such row. 070618 14:39:17 InnoDB: ERROR: the age of the last checkpoint is 237829009, InnoDB: which exceeds the log group capacity 237813351. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of log files at least 10 times bigger than the InnoDB: largest such row. On 18/06/2007, at 12:09 PM, Baron Schwartz wrote: I'm out of ideas right now. I don't actually use mysqldump that much and have never had this happen. Hopefully someone else on the mailing list can help, or perhaps you can try #mysql on Freenode IRC. Baron Hartleigh Burton wrote: No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in row 1 of `trackdata` that it does not like. This table contains a long blob field which at present does not contain any more than ~80MB per row. I also use the --hex-blob flag for mysqldump to try and get around any possible problems with exporting this data... I have no descriptive error messages anywhere and it is driving me nuts :| On 18/06/2007, at 11:27 AM, Baron Schwartz wrote: Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, "ready for connections" notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator & mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in row 1 of `trackdata` that it does not like. This table contains a long blob field which at present does not contain any more than ~80MB per row. I also use the --hex-blob flag for mysqldump to try and get around any possible problems with exporting this data... I have no descriptive error messages anywhere and it is driving me nuts :| On 18/06/2007, at 11:27 AM, Baron Schwartz wrote: Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, "ready for connections" notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator & mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator & mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator & mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
mysqldump problem with large innodb tables...
Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator & mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. If anyone can help me out with this problem the assistance is greatly appreciated. I have scoured google and various other sources and not found much information that has been useful to me. I hope I have enough info below... if more is required let me know. mysqldump example P:\>mysqldump -u username -p mraentertainment > mraentertainment.sql --opt --verbose --max_allowed_packet=500M --hex-blob --single_transaction --net_buffer_length=100M Enter password: ** -- Connecting to localhost... -- Retrieving table structure for table albums... -- Sending SELECT query... ... -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 my.ini configuration file [client] port=3306 [mysql] default-character-set=latin1 [mysqld] log-bin=itd002-bin server-id=1 port=3306 wait_timeout=86400 max_allowed_packet=100M basedir="C:/Program Files/MySQL/MySQL Server 5.0/" datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/" default-character-set=latin1 default-storage-engine=INNODB sql- mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" max_connections=100 query_cache_size=0 table_cache=256 tmp_table_size=77M thread_cache_size=8 #*** MyISAM Specific options myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G myisam_sort_buffer_size=154M key_buffer_size=130M read_buffer_size=64K read_rnd_buffer_size=256K sort_buffer_size=256K #skip-innodb innodb_additional_mem_pool_size=6M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=3M innodb_buffer_pool_size=252M innodb_log_file_size=126M innodb_thread_concurrency=8 Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
