<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Read on FromDual GmbH</title><link>https://www.fromdual.com/tags/read/</link><description>Recent content in Read on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Tue, 24 Jul 2012 09:13:47 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/read/index.xml" rel="self" type="application/rss+xml"/><item><title>When a MySQL table was last touched</title><link>https://www.fromdual.com/blog/mysql-table-last-touched/</link><pubDate>Thu, 02 Jun 2011 20:56:29 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mysql-table-last-touched/</guid><description>&lt;p&gt;In our last customer project we had around 600 Gbyte of data in a MySQL database. Because this database consumed a significant amount of our disk space and backups with the InnoDB backup tool took pretty long we wanted to find out if we could get rid of some of the tables.&lt;/p&gt;</description></item><item><title>Reading other processes memory</title><link>https://www.fromdual.com/blog/reading-other-processes-memory/</link><pubDate>Fri, 14 Aug 2009 14:49:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/reading-other-processes-memory/</guid><description>&lt;p&gt;As you probably have experienced yet MySQL does not always provide all internal information as you might want to have them and as you are used to have from other RDBMS.&lt;/p&gt;</description></item></channel></rss>