Re: 90GB table on Windows 2000

If you're talking big datawarehouses with big tables, imagine no constraints or at least non-validated ones. On a prototype, I did enable/validate the main PK constraint... it took 5 DAYS! And yes, my development system is a Sun E450 with 4 400Mhz UltraSparc 2 CPUs (and Solaris 8). The Production system will be a SunFire 480.

Another useful tidbit... when you create the primary key, create the non-unique partitioned index on the PK columns first. Then the primary key using this index. I've found, not only does that save you from not losing the index when disabling the PK, creating the index in parallel on 4 CPUs is at least 4 times faster than letting Oracle do it for you while it creates/enables the PK... Oracle doesn't seem to know how to do this in parallel?

Oracle also did not give me a warm reponse on the idea of disable/enable or validate of constraints on a partition by partition basis (like rebuilding indexes a partition at a time). I thought this was a nifty idea.
john.

Daniel Morgan <dmorgan_at_exesolutions.com> wrote in message news:<3DAD8BBE.283905CD_at_exesolutions.com>...
> John Summers wrote:
>
>
> I can't imagine any table without constraints. So I have never done a partitioned table any other way.
>
> But my reason for suggesting you get a real O/S is that 90GB of data in a multiuser environment will tax
> Windows. And getting a 64 bit O/S won't hurt.
>
> Daniel Morgan
Received on Tue Oct 29 2002 - 11:39:11 CST