Thanks for the response.
The problem is that this behaviour seems to be happening even when the index
defining the uniqueness is not clustered.
Cheers,
Steve.
Remove the 'NOSPAM.' to send me e-Mail
> Article: 213494 of microsoft.public.sqlserver.programming
> It depends on the structure of the table and the clustered index on that
> table - If you are entering records into the table that will be inserted
> into the middle of the table the rest of the table needs to be reorder and
> therefore will get slower as the table fills up - Maybe look at using an
> alternative clustered index
> > Hi,
> > If I have a table with a unique index/constraint on a GUID column (which,
> > includes using it as a primary key), then inserts to the table get
> progressively
> > slower and slower as more records are added.
> > However, if I specify that the index is non-unique, then this slowing
> effect is
> > either not noticeable, or not present at all.
> > Is it normal for the slowing, and is there anything I can do about it,
> other
> > than not have the unique constraint on the index?
> > Cheers,
> > Steve.
> > Remove the 'NOSPAM.' to send me e-Mail