This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Do you have an URL that shows the official document on crash recovery for InnoDB from MySQL?
You know, MySQL does have a website. And it's extremely comprehensive. When I used "crash recovery for InnoDB from MySQL" for my Google keywords it led me directly to this page in the MySQL Reference Manual. I answered your original question tersely because it was a question which was also easily researched.
I'd say it pretty much depends on what does everybody understand under "crash recovery". The database I currently work with can be configured in such a way that data from every single committed transaction can be recovered from backups and redo logs, even in case of media failure. It seems to be a different concept from the one described by the link provided by Paul, though with proper backup strategy maybe similar level of protection could be achieved in MySQL - I don't know MySQL at all.
On the other hand, it also depends on how much value you put on the data in the database. For a social networking site, losing one day worth of data might be not that dramatic problem. For a bank, the same might be a disaster that could put the bank out of business. Both of these enterprises might clearly be labelled "serious business".
Joined: Mar 04, 2008
Martin Vajsar wrote: ... The database I currently work with can be configured in such a way that data from every single committed transaction can be recovered from backups and redo logs, even in case of media failure. ...
This is the crash recovery I am looking for. I know Oracle can do it and has tools to help you, but not so sure about MySQL.
Tejas Jain wrote:This is the crash recovery I am looking for. I know Oracle can do it and has tools to help you, but not so sure about MySQL.
It also depends on the infrastructure in your organization.
If there is a DBA that will take care of your database, and he is not willing to support MySQL, there is probably not much more to talk about. If there is not a database that would meet your needs at all, then you'll probably have to hire a new DBA or train somebody to become a DBA of a new database, and at this time additional factors might pop up, but this would probably be a rare situation.
And yes, you do need a DBA to take care of the database. If you're concerned about recovery in case of media failure, you definitely need somebody skilled enough to be absolutely sure of what he is doing to the database.