Re: splitting a big table

Am Donnerstag, 09.01.03 um 19:20 Uhr schrieb Christian Pekeler:

>> I wouldn't try having the same entity for both. That seems like 
>> asking for trouble.
>
> I don't expect it to be trivial. What kind of troubles do you expect?
>
>
>> If you want, you could create the second duplicate entity in code
>
> If I would go with two entities, I might as well create them in 
> EOModeler.
>
>
>> PS:  Most databases should be fine with lots and lots of rows in a 
>> table. I wouldn't do any of this unless you have actually run into a 
>> problem, or have some specific reason to think there will be a > 
>> problem.
>
> I am running into a problem. The table has over 40 million records and 
> it is getting slow.
>

If it's retrieval speed: if you get 10000 records each day and if you 
copy them daily from "new" to "old" you will have in 101 days 1 Mio 
records in old and 10000 in new. Will "new" really do any good, if 99% 
of all querys will need to hit "old" ?

Is the problem that the 40 mio records are mostly cruft ?

Ciao
	Nat!
------------------------------------------------------
Hence, if the present world doth go astray,
In you the cause is, be it sought in you;
And I therein will now be thy true spy. - Alighieri