tags:

views:

129

answers:

1

Would it be wise to use ROWLOCK on an insert statement that is copying large amounts of data and inserting it into the same table?

Ex)

INSERT INTO TABLE with (rowlock) (id, name) 
   SELECT newid, name 
   FROM TABLE with (nolock) 
   WHERE id = 1

Does anybody have recommendations on how to improve this statement, as I see when SQL Server gets busy it will end in Timeout Query returned for SQL Server.

A: 

You're probably better off storing the sub-query result in a temporary table before and insert that.

jfrobishow