Introduction of OPTIMIZE_FOR_SEQUENTIAL_KEY = ON

  • Hi,

    We have low latency high volume system.

    I have a table having 3 columns (2 int and 1 bigint) as primary non clustered key . This table is expected to store 3o million + records each day. At the end of the day the table will be cleared empty. Now the record in this table will be inserted using BCP from VC++ application and it is expected that 200000 records per second will be inserted in this table.

    What i have read online is to introduce another column (Identity) as clustered index that will monotonically increase for each record with  OPTIMIZE_FOR_SEQUENTIAL_KEY = ON. This will reduce the page latch wait types thus increasing the efficiency of insertion which .

    Is this correct implementation.

    Regards,

    Saumik

  • How will the data be used, other than for INSERTs?


Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply