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 dat
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
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
things a little. I think partitioning is the way to go and you should
use MERGE tables to handle your partitions. Really what you are
lookin
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
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
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,0
Hello,
I am seeking information on best practices with regards to Data Warehousing
and MySQL. I am considering moving to PostgreSQL.
I am currently using MySQL as the database of choice. I am now running into
performance issues with regards to large tables.
At the moment, I have the
I dont think the types of tables will really help you, because as I understand it
mySQL doesnt yet have stored procs, views, and sub-selects, regardless of table type...
I may be wrong though...
Taylor Lewick
Unix System Administrator
Fortis Benefits
816 881 6073
"Help Wanted. Seeking Telepat
Hi guys,
Does anyone have any thoughts on using MySQL for a datawarehousing application?
Problems I've run in to are with mining data from a data warehouse because of the lack
of sub-selects, stored procs, and views.
Should I be looking more at InnoDB or MyISAM table types?
any thoughts are a
In the last episode (May 17), Brad Teale said:
> We are warehousing real-time data. The data is received at up to T1 speeds,
> and is broken up and stored into the database in approximately 25 different
> tables. Currently MySQL is doing terrific, we are using MyISAM tables and
> are storing 24
: Friday, May 17, 2002 12:27 PM
To: Brad Teale
Cc: '[EMAIL PROTECTED]'
Subject: Re: Real-time data warehousing
How are your apps written? We use OTL libaries from
http://members.fortunecity.com/skuchin/home.htm
which are compiled into our C/C++ code. Moving our apps from oracle to mysql
onl
On Friday 17 May 2002 12:58 pm, Brad Teale wrote:
> I forgot to mention, we have Oracle in-house, and the machine the MySQL
> database will reside on is a 2 proc Sun box with 1.5G of RAM. The Oracle
> databases reside on a 16 proc Sun box with 10G of RAM.
How are your apps written? We use OTL
, how much of a performance hit would we take with
MySQL if we connected through MyODBC?
Thanks again,
Brad
-Original Message-
From: walt [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 11:47 AM
To: Brad Teale
Cc: '[EMAIL PROTECTED]'
Subject: Re: Real-time data warehousing
Brad Teale wrote:
> We are warehousing real-time data. The data is received at up to T1 speeds,
> and is broken up and stored into the database in approximately 25 different
> tables. Currently MySQL is doing terrific, we are using MyISAM tables and
> are storing 24 hours worth of data but we d
]
[EMAIL PROTECTED]
- Original Message -
From: "Brad Teale" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 17, 2002 6:49 PM
Subject: Real-time data warehousing
> We are warehousing real-time data. The data is received at up to T1
speeds,
>
We are warehousing real-time data. The data is received at up to T1 speeds,
and is broken up and stored into the database in approximately 25 different
tables. Currently MySQL is doing terrific, we are using MyISAM tables and
are storing 24 hours worth of data but we don't have any users and we
Hi all,
Two easy pieces :-):
1)Anybody has experience in using MySQL for data warehousing?
2)Anybody has tried to implement OLAP engine for data warehousing using
MySQL???
I thank You in advance!
Have a nice day ...
--
Dr. Corrado Topi
Manger of the Special Projects Unit
Elbi International
21 matches
Mail list logo
