Comments on: A progress report on MySQL Table Sync http://www.xaprb.com/blog/2007/04/02/a-progress-report-on-mysql-table-sync/ Stay curious! Thu, 24 Jul 2008 00:23:35 +0000 http://wordpress.org/?v=2.2.2 By: Xaprb http://www.xaprb.com/blog/2007/04/02/a-progress-report-on-mysql-table-sync/#comment-5468 Xaprb Tue, 03 Apr 2007 15:11:37 +0000 http://www.xaprb.com/blog/2007/04/02/a-progress-report-on-mysql-table-sync/#comment-5468 <p>Yes, that would work too, though it could be a lot of work on large tables. Do you think I should add an option to do that if the DBA thinks it's the best way?</p> <p>I already looked into ALTER TABLE ... DISABLE KEYS but that only disables non-unique keys.</p> Yes, that would work too, though it could be a lot of work on large tables. Do you think I should add an option to do that if the DBA thinks it’s the best way?

I already looked into ALTER TABLE … DISABLE KEYS but that only disables non-unique keys.

]]> By: Scott Noyes http://www.xaprb.com/blog/2007/04/02/a-progress-report-on-mysql-table-sync/#comment-5467 Scott Noyes Tue, 03 Apr 2007 15:08:24 +0000 http://www.xaprb.com/blog/2007/04/02/a-progress-report-on-mysql-table-sync/#comment-5467 <p>A fourth way to do that update is to drop the indexes and recreate them after the update is complete.</p> A fourth way to do that update is to drop the indexes and recreate them after the update is complete.

]]>