er into MySQL's partitioning.
Cheers
- Andrew
-Original Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Friday, 27 July 2007 6:44 PM
To: mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs PostgreSQL
On 7/26/07, Andrew Armstrong wrote:
> * Table 1: 8
On 7/26/07, Andrew Armstrong wrote:
> * Table 1: 80,000,000 rows - 9.5 GB
> * Table 2: 1,000,000,000 rows - 8.9 GB
> This is a generic star schema design for data warehousing.
> I have read that it is better if perhaps partitioning is implemented, where
> new data is added to a partiti
007 10:23 AM
To: Andrew Armstrong
Cc: 'Wallace Reis'; mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs PostgreSQL
Wallace is right, Data Warehousing shouldn't delete any data. MySQL
isn't as robust as say, Oracle, for partitioning so you need to fudge
thing
after a week, etc.
I'm more concerned as to why inserts begin to slow down so much due
to the
large table size.
-Original Message-
From: Wallace Reis [mailto:[EMAIL PROTECTED]
Sent: Friday, 27 July 2007 1:02 AM
To: Andrew Armstrong
Cc: mysql@lists.mysql.com
Subject: Re: Data War
I'm more concerned as to why inserts begin to slow down so much due to the
large table size.
-Original Message-
From: Wallace Reis [mailto:[EMAIL PROTECTED]
Sent: Friday, 27 July 2007 1:02 AM
To: Andrew Armstrong
Cc: mysql@lists.mysql.com
Subject: Re: Data Warehousing and MySQL vs
On 7/26/07, Andrew Armstrong <[EMAIL PROTECTED]> wrote:
Do you have a suggestion to how this should be implemented?
Data is aggregated over time and summary rows are created.
I think that you didnt design correctly your DW.
It should have just one very larger table (the fact table).
Data should
Warehousing and MySQL vs PostgreSQL
On 7/26/07, Andrew Armstrong <[EMAIL PROTECTED]> wrote:
>
> 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 aggrega
On 7/26/07, Andrew Armstrong <[EMAIL PROTECTED]> wrote:
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
: Re: Data Warehousing and MySQL vs PostgreSQL
On Thu, 2007-07-26 at 18:37 +1000, Andrew Armstrong wrote:
> Hello,
>
>
>
> I am seeking information on best practices with regards to Data
Warehousing
> and MySQL. I am considering moving to PostgreSQL.
> * Table 1: 80,
On Thu, 2007-07-26 at 18:37 +1000, Andrew Armstrong wrote:
> Hello,
>
>
>
> I am seeking information on best practices with regards to Data Warehousing
> and MySQL. I am considering moving to PostgreSQL.
> * Table 1: 80,000,000 rows - 9.5 GB
> * Table 2: 1,000,000,000 rows - 8.9 GB
Ju
10 matches
Mail list logo
