update strategies
From: PA (peeyush.agrawal_at_cendant.com)
Date: 03/09/04
- Next message: Joe Celko: "Re: Aggregating by time period"
- Previous message: Steve Kass: "Re: simple question re DELETEing in linked DB"
- Next in thread: Steve Kass: "Re: update strategies"
- Reply: Steve Kass: "Re: update strategies"
- Reply: Louis Davidson: "Re: update strategies"
- Reply: Joe Celko: "Re: update strategies"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Mar 2004 12:12:53 -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 .
- Next message: Joe Celko: "Re: Aggregating by time period"
- Previous message: Steve Kass: "Re: simple question re DELETEing in linked DB"
- Next in thread: Steve Kass: "Re: update strategies"
- Reply: Steve Kass: "Re: update strategies"
- Reply: Louis Davidson: "Re: update strategies"
- Reply: Joe Celko: "Re: update strategies"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
