Hey Baron,
Your blog post was quite informative; your suggestion to use a
combination of merged MyISAM tables and InnoDB for the live partition
made a lot of sense, and it sounds like the path I'll need to follow.
I appreciate the information!
Baron Schwartz wrote:
Hi,
I'll just address
Hi,
I'll just address the things others didn't answer.
On Thu, Apr 3, 2008 at 2:28 PM, Dre [EMAIL PROTECTED] wrote:
1) Several sources seem to suggest MyISAM is a good choice for data
warehousing, but due to my lack of experience in a transaction-less world,
One approach you might consider
Hey folks,
I'm currently deciding whether to build a decent sized (around
300-500GB, although honestly, I've got little to base that on at the
moment) data warehouse in postgreSQL or MySQL. I've developed several
in MS SQL and postgreSQL, but the client is comfortable with MySQL, and
I'd
I've built several datamarts using perl and MySQL. The largest ones
have been up to about 30GB, so I'm not quite on your scale.
for #1, I have an etl_id in the fact table so I can track back any
particular ETL job. I typically make it a dimension and include date,
time, software version, etc.
On Thu, Apr 3, 2008 at 2:28 PM, Dre [EMAIL PROTECTED] wrote:
1) Several sources seem to suggest MyISAM is a good choice for data
warehousing, but due to my lack of experience in a transaction-less world,
this makes me a little nervous.
MyISAM has the advantage of very fast loading. It's much
