Exactly what will happen. The table will hose when it reaches (through appends, etc.) the linit.
If you are using tables that large, and I personally prefer a 50% margin of safety, it is time to upsize to SQL server
and communicate via SQL.
Another risk of using tables that size, especially if there are several that are related, is that your queries could potentially run out of memory, and/or temporary cursors could go past the limit as well, and will self-destruct.
>
>Could it be the size limitation also cause problem of
>data corruption either at the end or middle of the free table
>like I encountered before ?
>
>In my case, it reported of 'not a database file' when
>I use a third party program to view it.
MSCE, MCSP, Microsoft Channel Partner
Relax, Boss. We will meet the deadline! What? You want to add MORE? What do you mean, Over Budget?
Opinions and comments are the sole responsibility of the sender, and accuracy, correctness, or pertinence is considered coincidental.
