2

I have a table with field Id (bigint, IDENTITY) as primary key and clustered index on it. I inserted 400 rows and saw execution plan. I got: the relative query cost for this insertion 36% and for this query "Clustered Index Insert"'s cost 97%. What's going on? Why does it work so slow?

ADDED:

enter image description here

continue enter image description here

See also SQL Server insert performance

Community
  • 1
garik
  • 6,782
  • 10
  • 44
  • 56

1 Answers1

2

The relative cost of the components of an execution plan is not always reliable.

The INSERTED scan or deleted scan shouts TRIGGER to me. This is your problem most likely.

Are you looping over 400 rows and sending an email in an extreme example?

gbn
  • 70,237
  • 8
  • 167
  • 244