RE: Slow insert into a table – SQLServerCentral

SSC Guru

Points: 323504

February 11, 2014 at 8:09 am

don't get caught up staring at the percentages; they have to add up to 100, so just because something is 75% doesn't mean it's bad, it just means that's where work was performed compared to other steps.

i put more importance on things like the estimated number of rows inserted being 19213 and the estimated subtree cost being 87.8014 than anything else.

you said it inserts one at a time, but this looks set based.

can you obfuscate the insert statement and show it to us? the actual execution plan would tell us everything, if you can post that.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!