August 12, 2008 at 3:09 pm
We are using the timestamp datatype feature to notify users when records change. So when something is updated we go to the parent and update it. If I had a statement like below where the ID is the PrimaryKey and updated it to itself to change the timestamp would it want to reindex the clustered key?
Update Table1
Set Id = Id
Where Id = @Idpassedin
Should I use a non-indexed field so that I improve performance?
August 12, 2008 at 7:48 pm
No... it should be ok.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply