Comments on: Innodb Undelete and Sphinx Support http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/ Everything about MySQL Performance Sat, 07 Nov 2009 18:35:44 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Data Recovery Toolkit for InnoDB Version 0.1 Released | MySQL Performance Blog http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/comment-page-1/#comment-207427 Data Recovery Toolkit for InnoDB Version 0.1 Released | MySQL Performance Blog Wed, 28 Nov 2007 09:29:52 +0000 http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/#comment-207427 [...] Peter mentioned in one of previous posts, we’ve done huge work developing robust strategies of InnoDB data [...] [...] Peter mentioned in one of previous posts, we’ve done huge work developing robust strategies of InnoDB data [...]

]]> By: Data Recovery Toolkit | Life without names http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/comment-page-1/#comment-206090 Data Recovery Toolkit | Life without names Tue, 27 Nov 2007 13:54:44 +0000 http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/#comment-206090 [...] Peter mentioned in one of previous posts, we’ve done huge work developing robust strategies of InnoDB data [...] [...] Peter mentioned in one of previous posts, we’ve done huge work developing robust strategies of InnoDB data [...]

]]> By: peter http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/comment-page-1/#comment-191954 peter Tue, 13 Nov 2007 16:28:44 +0000 http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/#comment-191954 Sinisa Absolutely. I think I generally pointed out you can't always recover data 100% and MyISAM is indeed the case when some data going to be overwritten by delete operation. If you look at the details of how we offer recovery services in general you'll see access (for free) how much of the data is possible to recover and only proceed with real recovery if customer understands all implications about recovered data. Because we only charge on success basics we need to ensure we're on the same page. Sinisa

Absolutely. I think I generally pointed out you can’t always recover data 100% and MyISAM is indeed the case when some data going to be overwritten by delete operation.

If you look at the details of how we offer recovery services in general you’ll see access (for free) how much of the data is possible to recover and only proceed with real recovery if customer understands all implications about recovered data. Because we only charge on success basics we need to ensure we’re on the same page.

]]> By: Sinisa Milivojevic http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/comment-page-1/#comment-191946 Sinisa Milivojevic Tue, 13 Nov 2007 16:17:02 +0000 http://www.mysqlperformanceblog.com/2007/11/12/innodb-undelete-and-sphinx-support/#comment-191946 Peter, This is truly a nice service. However ... I think you have not stressed enough on all "IF's" and "MAY BE's" when it comes to MyISAM undelete. In MyISAM, there will be ALWAYS a number of columns that can not be undeleted. This number depends on the size of offset pointer, number of NULLable columns and on the size of columns themselves, those at the start of the row. We, at MySQL Support, provide undelete service for MyISAM, only when it is feasible and for a definite niche of customers. This is due to the fact that undeleting requires writing dedicated programs, especially when dealing with packed records, which are most frequent type of MyISAM tables. Peter,

This is truly a nice service. However …

I think you have not stressed enough on all “IF’s” and “MAY BE’s” when it comes to MyISAM undelete. In MyISAM, there will be ALWAYS a number of columns that can not be undeleted. This number depends on the size of offset pointer, number of NULLable columns and on the size of columns themselves, those at the start of the row.

We, at MySQL Support, provide undelete service for MyISAM, only when it is feasible and for a definite niche of customers. This is due to the fact that undeleting requires writing dedicated programs, especially when dealing with packed records, which are most frequent type of MyISAM tables.

]]>