http://www.karan.org/blog/index.php?disp=comments en-US http://backend.userland.com/rss 60 Tue, 26 May 2009 17:39:30 +0000 Scott H [Visitor] c4915@http://www.karan.org/blog/ Just be careful with this. Obviously if you're deleting a whole lot of data you must be "in charge" of that table: but DELETE is friendlier than DROP to things that rely on triggers such as replication. Marcus Hagander recently posted a good tip for administrators to keep on top of this sort of thing:<br /> <br /> <a href="http://blog.hagander.net/archives/142-Why-are-you-not-logging-your-DDL.html">http://blog.hagander.net/archives/142-Why-are-you-not-logging-your-DDL.html</a>
http://blog.hagander.net/archives/142-Why-are-you-not-logging-your-DDL.html]]> http://www.karan.org/blog/index.php/2009/05/26/removing-lots-of-data-from-a-db-table#c4915 Tue, 26 May 2009 12:00:03 +0000 Karanbir Singh [Member] c4914@http://www.karan.org/blog/ artms,<br /> <br /> 'truncate' works quite nicely too. Thanks for pointing that out - however I've had issues with truncate on mysql db's when there were external references / foreign keys.
'truncate' works quite nicely too. Thanks for pointing that out - however I've had issues with truncate on mysql db's when there were external references / foreign keys.]]> http://www.karan.org/blog/index.php/2009/05/26/removing-lots-of-data-from-a-db-table#c4914 Tue, 26 May 2009 11:05:59 +0000 artms [Visitor] c4913@http://www.karan.org/blog/ You can also "truncate table rawdata" which is also faster then delete http://www.karan.org/blog/index.php/2009/05/26/removing-lots-of-data-from-a-db-table#c4913