Re: Documentation for reasons to NOT use RAC?
From: Greg Rahn <greg_at_structureddata.org>
Date: Mon, 22 Feb 2010 07:48:59 -0800
Message-ID: <a9c093441002220748h7e071e4fk8f08eae6e221bb14_at_mail.gmail.com>
I'm quite certain you will find such papers right next to "Why you dont need Oracle, MySQL solves the world's database problems" :)
> I'm being pulled into a meeting later this morning to answer why we
> shouldn't put every db in RAC? Any white papers etc, stating why its a bad
> idea?
Date: Mon, 22 Feb 2010 07:48:59 -0800
Message-ID: <a9c093441002220748h7e071e4fk8f08eae6e221bb14_at_mail.gmail.com>
I'm quite certain you will find such papers right next to "Why you dont need Oracle, MySQL solves the world's database problems" :)
Generally I find that such papers are 99% emotion, 1% fact, so they really dont stand up very well under scrutiny. It's probably best for you and your org to do the pros vs cons whiteboard and have a healthy discussion.
At the end of the day I'd just ask the million dollar questions -
"What problem does this technology solve? How does it do so? What are
the alternatives?"
That will probably be more productive than you loading up your gun
full of unverified 3rd party experiences.
On Mon, Feb 22, 2010 at 4:52 AM, <TESTAJ3_at_nationwide.com> wrote:
>
> I'm being pulled into a meeting later this morning to answer why we
> shouldn't put every db in RAC? Any white papers etc, stating why its a bad
> idea?
-- Regards, Greg Rahn http://structureddata.org -- http://www.freelists.org/webpage/oracle-lReceived on Mon Feb 22 2010 - 09:48:59 CST