>>Thanks, why would a stored procedure be a bad idea for inserting one record? I had learnt this technique from Kevin McNeish (sp?) in Mere Mortals for .Net so thought it would be a good practice that all updates go through a stored procedure.
>>
>
>I think the question was whether this procedure was being used inside of some loop or other looping construct to insert a large number of rows in one shot, one row at a time.
>
>If that was the case, it's better to send in XML or a table type (new in SQL 2008).

Or just use BULK INSERT.