Richard Fryar (9/2/2008)
Check for an insert trigger.I've seen ridiculously inefficient triggers resulting in high CPU and IO.
That is indeed a good one, Richard, and one that is often simply overlooked!
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service