update Strategies
From: PA (peeyush.agrawal_at_cendant.com)
Date: 03/08/04
- Next message: Vishal Parkar: "Re: Using SELECT TOP with a variable"
- Previous message: anonymous_at_discussions.microsoft.com: "RE: select range of dates"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Mar 2004 15:38:23 -0500
I am trying to find out if there is any difference (in terms of performance)
between a partial update or a full update of a row in sql server. Currently
we have store procedures that take care of updates for a table (partial or
full). Is it worth to have that logic in the data access layer for partial
updates and sending the sql statement sent over to sql server rather then
sql server executing the whole store procedure to do any partial update? I
know that in an update sql server deletes and then inserts the row but is it
done differently when it is not updating the index fields (clustered). If
somebody could help me out with this issue I would really appreciate. Please
recommend your update strategies .
Thanks in advance
- Next message: Vishal Parkar: "Re: Using SELECT TOP with a variable"
- Previous message: anonymous_at_discussions.microsoft.com: "RE: select range of dates"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
