Do you have a suggestion to how this should be implemented? Data is aggregated over time and summary rows are created.
-----Original Message----- From: Wallace Reis [mailto:[EMAIL PROTECTED] Sent: Thursday, 26 July 2007 8:43 PM To: Andrew Armstrong Cc: mysql@lists.mysql.com Subject: Re: Data Warehousing and MySQL vs PostgreSQL On 7/26/07, Andrew Armstrong <[EMAIL PROTECTED]> wrote: > <snip> > Information is deleted from this DW as well, after every five minutes. > The data being recorded is time sensitive. As data ages, it may be deleted. > Groups of samples are aggregated into a summary/aggregation sample prior to > being deleted. > I believe this is starting to cause fragmentation issues (please correct me > if I am wrong) where old, deleted row positions get re-used by new rows on > disk. There's something wrong. DW is a non-volatile database. Meaning that data in the database is never over-written or deleted, once committed, the data is static, read-only, but retained for future reporting. -- wallace reis/wreis Núcleo de Biologia Computacional e Gestão de Informações Biotecnológicas/LABBI -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
