Re: splitting a big table

> 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.


Christian