On Dec 17, 7:25 am, Robert Klemme <shortcut..._at_googlemail.com> wrote:
> On 17 Dez., 11:26, "Wilfrid" <grill..._at_yahoo.com> wrote:
>
> > Would their be any reason why removing a primary key and recreating it on a
> > reasonibly large table (~160000 records and increasing at steady rate, with
> > int, nvarchar, bit and datetime columns), would have an impact on select and
> > insert performance?
> > Is there some kind of fragmentation on a table that could explain this?
> > thanks in advance for your insight
>
> Richard Foote wrote quite a bit about this:http://richardfoote.wordpress.com/2007/12/11/index-internals-rebuildi...http://www.miracleas.dk/images/upload/Docs/Richard%20Foote.pdf
>
> Kind regards
>
> robert
I think when you drop and then add the primary key it causes the data
in the table to reorginize which is similar to a performance tuning
change.
Meaning if you had fragmented data you organize it.
Received on Mon Dec 17 2007 - 14:24:17 CST
