>>
>>"Mad" Matt, good to see you. Where you been lately?
>>
>
>busy as heck. doing mostly observing instead of posting.
>
>
>>Makes you wonder about the EuroTunnel doesn't it? That thing's more than 2 gig, yet they've managed to find a workaround that meets their performance needs.
>
>EuroTunnel uses a single table that's over 2 GB?? I thought that wasn't possible? {Although I've got a couple of Dragan's lightbulbs now -g-}
>
>In any case. I agree with Ed that hard rules shouldn't be set, but I still think that trying to account for the 2GB barrier may be counter productive.
>
>BTW - can you elaborate on what you know about EuroTunnel? Is there a developer's website that has some info. I'm very curious.

I can just how such construction might work. Let's say we have one-many pair where many side going over 2G. So, you split 'many' table on 2 or more parts and add one more field to 'one' table to store alias of corresponding 'many' table, i.e. before checking foreign key your app will check first in what table to go.