Comments on: MySQL Crash Recovery http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/ Everything about MySQL Performance Fri, 05 Dec 2008 10:16:42 +0000 http://wordpress.org/?v=2.5.1 By: Goodbye FRM (or at least the steps to it) | Ramblings http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-372892 Goodbye FRM (or at least the steps to it) | Ramblings Thu, 06 Nov 2008 03:56:58 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-372892 [...] As for if you crash during a table rename (with any engine with its own data dictionary.. e.g. InnoDB)… you again get to keep both pieces. (There is a bit of discussion on this over here) [...] [...] As for if you crash during a table rename (with any engine with its own data dictionary.. e.g. InnoDB)… you again get to keep both pieces. (There is a bit of discussion on this over here) [...]

]]> By: zlatan24 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-359364 zlatan24 Fri, 03 Oct 2008 11:10:47 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-359364 I heard about not bad application-<a href="//www.recoverytoolbox.com/sql.html\" rel="nofollow">sql server recovery</a>, this tool can process huge databases, their file size can reach 16 TB, recovery Toolbox for SQL Server supports data extraction via the local area network, you can save recovered data as SQL scripts, it is also possible to split data into files of any size, this tool can save extracted information directly to the SQL server. It allow to recovery SQL Server faster, is compatible with all supported versions of Microsoft Windows, such as Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP, Windows XP SP2, Windows 2003 Server, Windows Vista. I heard about not bad application-sql server recovery, this tool can process huge databases, their file size can reach 16 TB, recovery Toolbox for SQL Server supports data extraction via the local area network, you can save recovered data as SQL scripts, it is also possible to split data into files of any size, this tool can save extracted information directly to the SQL server. It allow to recovery SQL Server faster, is compatible with all supported versions of Microsoft Windows, such as Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP, Windows XP SP2, Windows 2003 Server, Windows Vista.

]]> By: Kleyber http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-324937 Kleyber Tue, 08 Jul 2008 20:13:28 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-324937 Hi, I have a big problem here: We have noticed that our server was hanging up without any reason, apparently. So, we have made a backup (using MySQLDump) and we had to reinstall everything (Linux server, Apache, MySQL) and when we tried to restore the .SQL file, we noticed that in a certain point of the file, there is some strange data, but the file is very big (490 MB) to be opened for any editor. My question is: How to recover this .SQL file? Is there any editor which opens that file? Thanks in advance, Hi,

I have a big problem here: We have noticed that our server was hanging up without any reason, apparently. So, we have made a backup (using MySQLDump) and we had to reinstall everything (Linux server, Apache, MySQL) and when we tried to restore the .SQL file, we noticed that in a certain point of the file, there is some strange data, but the file is very big (490 MB) to be opened for any editor. My question is: How to recover this .SQL file? Is there any editor which opens that file?

Thanks in advance,

]]> By: SILENT HACKER http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-314652 SILENT HACKER Wed, 18 Jun 2008 01:21:23 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-314652 can any one tel me how to maintain your own log files for mysql? can any one tel me how to maintain your own log files for mysql?

]]> By: pablo http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-312637 pablo Thu, 12 Jun 2008 14:40:26 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-312637 Hi, can someone post the script which moves out all MyISAM tables out of MySQL database directory, checks them with MyISAMchk and moves them back to running server? Thanks in advance.. Hi, can someone post the script which moves out all MyISAM tables out of MySQL database directory, checks them with MyISAMchk and moves them back to running server? Thanks in advance..

]]> By: Project 2061 Techlog » Optimizing MySQL Server Runtime Parameters http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-296425 Project 2061 Techlog » Optimizing MySQL Server Runtime Parameters Wed, 07 May 2008 19:00:56 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-296425 [...] MySQL Performance Blog: MySQL Crash Recovery [...] [...] MySQL Performance Blog: MySQL Crash Recovery [...]

]]> By: TorrentBits - Page 51 - TORRENTs.RO http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-251158 TorrentBits - Page 51 - TORRENTs.RO Mon, 10 Mar 2008 10:31:20 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-251158 [...] (i think) Oh and if you have mysql log files then you can check there to see why crash occured MySQL Crash Recovery | MySQL Performance Blog ________________ Table 'user' is marked as crashed and should be repaired - Dev Shed [...] [...] (i think) Oh and if you have mysql log files then you can check there to see why crash occured MySQL Crash Recovery | MySQL Performance Blog ________________ Table ‘user’ is marked as crashed and should be repaired - Dev Shed [...]

]]> By: peter http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-176803 peter Fri, 12 Oct 2007 16:55:03 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-176803 gigiduru, This is again wrong comparison. Innodb can mean both speed AND safety in many cases. Though MyISAM, MEMORY, ARCHIVE storage engines all can be faster for some workloads. Indeed you're right many people have heard MySQL has transactions but do not bother to check it is in case you're using Innodb tables. I never said MySQL is for everyone. But this blog is for people trying to get most out of their MySQL install as well as know how to avoid the issues. gigiduru,

This is again wrong comparison. Innodb can mean both speed AND safety in many cases. Though MyISAM, MEMORY, ARCHIVE storage engines all can be faster for some workloads.

Indeed you’re right many people have heard MySQL has transactions but do not bother to check it is in case you’re using Innodb tables.

I never said MySQL is for everyone. But this blog is for people trying to get most out of their MySQL install as well as know how to avoid the issues.

]]> By: gigiduru http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-176798 gigiduru Fri, 12 Oct 2007 15:37:00 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-176798 Just a little follow up, just take a look at these two web pages, and see if you notice something unusual: http://www.mysql.com/why-mysql/quality/ vs http://bugs.mysql.com/bug.php?id=30234 Just a little follow up, just take a look at these two web pages, and see if you notice something unusual:
http://www.mysql.com/why-mysql/quality/
vs
http://bugs.mysql.com/bug.php?id=30234

]]> By: gigiduru http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-176797 gigiduru Fri, 12 Oct 2007 15:34:16 +0000 http://www.mysqlperformanceblog.com/2006/07/30/mysql-crash-recovery/#comment-176797 So basically, you're saying that if I want to choose MyISAM speeed AND Innodb reliability, MySQL is not a choice... That's what I wanted to hear. It's all about vision. "MyISAM tables - yes these are not designed to be crash safe." - this is a total complete flop. If MySQL would have stayed in the realm of test/toy/web-serving realm, I wouldn't mind to deal with it. But touting and beating the drum that MySQL is enterprise ready... that's dangerous. You must be aware that there are companies out there that are doing even financial transactions, serving the clients from the myisam tables. I can hear the clock ticking. And at the philosophical level, I'm starting to believe that the majority of people choosing MySQL as their preferred database are prone to choose the path of minimal resistance - masking it under words like "efficiency", "simplicity is genius" (see the so much touted ease of use) - without giving a second thinking what's expecting them down on the road - THE minefield. Once they are in, they will defend their poor choice until death do them apart. But after all, it's JUST a poor choice, which can be corrected. And if you're giving me a response that it's all about making things better, improving and building on something that others already built, please... choose something more worthy. Postgresql it's MUCH more worthy in this regard. I know enough about MySQL but few things about PostgreSQL so it's kind of logic for me to reach this conclusion. So basically, you’re saying that if I want to choose MyISAM speeed AND Innodb reliability, MySQL is not a choice…
That’s what I wanted to hear.
It’s all about vision. “MyISAM tables - yes these are not designed to be crash safe.” - this is a total complete flop. If MySQL would have stayed in the realm of test/toy/web-serving realm, I wouldn’t mind to deal with it. But touting and beating the drum that MySQL is enterprise ready… that’s dangerous. You must be aware that there are companies out there that are doing even financial transactions, serving the clients from the myisam tables. I can hear the clock ticking.
And at the philosophical level, I’m starting to believe that the majority of people choosing MySQL as their preferred database are prone to choose the path of minimal resistance - masking it under words like “efficiency”, “simplicity is genius” (see the so much touted ease of use) - without giving a second thinking what’s expecting them down on the road - THE minefield. Once they are in, they will defend their poor choice until death do them apart. But after all, it’s JUST a poor choice, which can be corrected.
And if you’re giving me a response that it’s all about making things better, improving and building on something that others already built, please… choose something more worthy. Postgresql it’s MUCH more worthy in this regard. I know enough about MySQL but few things about PostgreSQL so it’s kind of logic for me to reach this conclusion.

]]>