Re: INSERT performance on large table.

The database has no trouble with tables with multi-million records. As long as its properly indexed, performance will be pretty good. Whether or not to stage the 4000 daily records depends on what they are for. Are the recording transactions that occur and are kept as a log of activity? Or are they new orders that need to be processed that night? If the latter, then a staging area is a good idea to avoid slowing down the nightly process by accessing a large table.

James Williams <techsup_at_mindspring.com> wrote in message news:3b004cef.36828967_at_news.mindspring.com...
> I have a user who wishes to initially load 4 million rows on a table.
> After this he will insert 4000 per day. I don't like this approach. I
> would like to maintain a small staging table and then let him have an
> archive area for the 4m plus rows.
>
>
> A table with 4m rows in it. What is the issue of an additional 4k rows
> each day from a performance standpoint.
>
Received on Mon May 14 2001 - 20:07:19 CDT