<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Dumping large MySQL InnoDB tables</title> <atom:link href="http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/feed/" rel="self" type="application/rss+xml" /><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/</link> <description>The Journal Of A Linux Sysadmin</description> <lastBuildDate>Wed, 08 Feb 2012 13:08:17 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3</generator> <item><title>By: Avinash Pawar</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-192509</link> <dc:creator>Avinash Pawar</dc:creator> <pubDate>Thu, 17 Mar 2011 04:55:30 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-192509</guid> <description>Thanks for this tips.</description> <content:encoded><![CDATA[<p>Thanks for this tips.</p> ]]></content:encoded> </item> <item><title>By: pmasajjage</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-182194</link> <dc:creator>pmasajjage</dc:creator> <pubDate>Tue, 10 Aug 2010 10:52:20 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-182194</guid> <description>Oh, never mind my previous post. I have found a link on this site with the answer.
http://www.ducea.com/2009/03/17/howto-get-a-small-sample-dataset-from-a-mysql-database-using-mysqldump/</description> <content:encoded><![CDATA[<p>Oh, never mind my previous post. I have found a link on this site with the answer.<br
/> <a
href="http://www.ducea.com/2009/03/17/howto-get-a-small-sample-dataset-from-a-mysql-database-using-mysqldump/" rel="nofollow">http://www.ducea.com/2009/03/17/howto-get-a-small-sample-dataset-from-a-mysql-database-using-mysqldump/</a></p> ]]></content:encoded> </item> <item><title>By: pmasajjage</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-182193</link> <dc:creator>pmasajjage</dc:creator> <pubDate>Tue, 10 Aug 2010 10:50:31 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-182193</guid> <description>This is a good tip. Is there a way to partially dump all the tables in the database say for each table only the first 500k records?</description> <content:encoded><![CDATA[<p>This is a good tip. Is there a way to partially dump all the tables in the database say for each table only the first 500k records?</p> ]]></content:encoded> </item> <item><title>By: Sam IT</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-181581</link> <dc:creator>Sam IT</dc:creator> <pubDate>Wed, 10 Feb 2010 19:52:50 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-181581</guid> <description>single-row locking is one of the main reasons I use InnoDB.Can you imagine an hourly backup on a Master MySQL server with a lot of data?The whole application &quot;freezes&quot; up.On the other hand, when you use this, you need to remember that since it doesn&#039;t lock the table, it&#039;s possible for new data to be inserted (which can also be a bad thing).For example, if you insert two lines per application &quot;event&quot;, you may only get one of the lines in the backup. The same goes for multiple tables with JOINs.If you insert multiple rows into multiple tables, there&#039;s a chance you&#039;ll get partial data.The safest way is to either lock all tables of deny access to the db server.To prevent downtime, it&#039;s recommended to setup slave servers, you can do pretty much anything you want on them (stop slave; mysqldump; start slave;).Good luck!</description> <content:encoded><![CDATA[<p>single-row locking is one of the main reasons I use InnoDB.</p><p>Can you imagine an hourly backup on a Master MySQL server with a lot of data?</p><p>The whole application &#8220;freezes&#8221; up.</p><p>On the other hand, when you use this, you need to remember that since it doesn&#8217;t lock the table, it&#8217;s possible for new data to be inserted (which can also be a bad thing).</p><p>For example, if you insert two lines per application &#8220;event&#8221;, you may only get one of the lines in the backup. The same goes for multiple tables with JOINs.</p><p>If you insert multiple rows into multiple tables, there&#8217;s a chance you&#8217;ll get partial data.</p><p>The safest way is to either lock all tables of deny access to the db server.</p><p>To prevent downtime, it&#8217;s recommended to setup slave servers, you can do pretty much anything you want on them (stop slave; mysqldump; start slave;).</p><p>Good luck!</p> ]]></content:encoded> </item> <item><title>By: Dagbok för 14 May 2009 &#124; En sur karamell</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-180337</link> <dc:creator>Dagbok för 14 May 2009 &#124; En sur karamell</dc:creator> <pubDate>Thu, 14 May 2009 20:11:55 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-180337</guid> <description>[...] Dumping large MySQL InnoDB tables &#124; MDLog:/sysadmin &#8212; 20:00 via [...]</description> <content:encoded><![CDATA[<p>[...] Dumping large MySQL InnoDB tables | MDLog:/sysadmin &mdash; 20:00 via [...]</p> ]]></content:encoded> </item> <item><title>By: links for 2008-11-12 &#171; Brent Sordyl&#8217;s Blog</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-178851</link> <dc:creator>links for 2008-11-12 &#171; Brent Sordyl&#8217;s Blog</dc:creator> <pubDate>Wed, 12 Nov 2008 14:03:36 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-178851</guid> <description>[...] Dumping large MySQL InnoDB tables &#124; MDLog:/sysadmin will not speed the process, but it will allow the live application to use the mysql database as normal without locking any tables and preventing the application to change the database. (tags: mysqldump) [...]</description> <content:encoded><![CDATA[<p>[...] Dumping large MySQL InnoDB tables | MDLog:/sysadmin will not speed the process, but it will allow the live application to use the mysql database as normal without locking any tables and preventing the application to change the database. (tags: mysqldump) [...]</p> ]]></content:encoded> </item> <item><title>By: grick</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-178745</link> <dc:creator>grick</dc:creator> <pubDate>Mon, 27 Oct 2008 10:10:58 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-178745</guid> <description>I love you :)</description> <content:encoded><![CDATA[<p>I love you <img
src='http://www.ducea.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: Arstan</title><link>http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/comment-page-1/#comment-73487</link> <dc:creator>Arstan</dc:creator> <pubDate>Wed, 29 Aug 2007 03:48:53 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/10/26/dumping-large-mysql-innodb-tables/#comment-73487</guid> <description>Thanks for the tips, I was exactly looking for it!</description> <content:encoded><![CDATA[<p>Thanks for the tips, I was exactly looking for it!</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: www.ducea.com @ 2012-02-08 15:30:52 by W3 Total Cache -->
