Use the same building blocks. Mixing and matching different server types made things really difficult for us. Also, for VLDBs use larger servers (ex. M5000) rather than smaller (ex. T2000). Having fewer larger servers seems to be better than more smaller in a really large warehouse env. We have a large (~100TB) warehouse DB on RAC. Initially, we built it on V440's/V445s/T2000s, but after many tough weeks and per Oracle's recommendation we replaced all 4 nodes with 2 M5000 nodes. Things are MUCH better ever sense. In addition to this we have made sure the app side is tuned well and can scale (partition exchanges, direct-path loading, compression, parallel query, etc). Thanks, Abdul --- On Fri, 3/19/10, Holvoet, Jo <jo.holvoet@xxxxxxxxxxxxx> wrote: From: Holvoet, Jo <jo.holvoet@xxxxxxxxxxxxx> Subject: RE: Best practices for Datawarehouse: RAC or Non-RAC To: "oracle list" <oracle-l@xxxxxxxxxxxxx> Date: Friday, March 19, 2010, 7:17 AM Is the exchange partition technique still useful if, besides inserts, you have quite a bit of data already in the DW that needs to updated as well ? mvg, Jo From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: donderdag 18 maart 2010 18:56 To: tim@xxxxxxxxx Cc: ravigaur1@xxxxxxxxx; oracle list Subject: Re: Best practices for Datawarehouse: RAC or Non-RAC On Wed, Mar 17, 2010 at 6:30 PM, Tim Gorman <tim@xxxxxxxxx> wrote: Respectfully, I'd recommend reading "http://www.evdbt.com/TGorman%20TD2009%20DWScale.doc"; I just spent a few minutes re-reading this. It is required reading for anyone even thinking of building a data warehouse. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com