Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1580
| From | Gene Wirchenko <genew@ocis.net> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: update field with the same value |
| Date | 2011-02-11 12:05 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <ei5bl61u0lt3d4ma7l78c7i2sbjlolfvj3@4ax.com> (permalink) |
| References | <a375a396-34fb-4b90-a4cf-f966939b0161@n16g2000prc.googlegroups.com> <Xns9E8964D22953FYazorman@127.0.0.1> <37015ddb-d725-40d9-b5e9-218144f2b08d@o7g2000prn.googlegroups.com> |
On Fri, 11 Feb 2011 11:14:55 -0800 (PST), migurus <migurus@yahoo.com>
wrote:
[snip]
>To see all pros and cons (complexity, extra effort, etc) I'd like to
>undesrtand is SQL Server smart not
>to update columns whose value was not changed?
It does not matter. You can not do anything about it either way.
And if you did find out, it could easily change in another release.
(You are tilting at windwheels.)
Sincerely,
Gene Wirchenko
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar
update field with the same value migurus <migurus@yahoo.com> - 2011-02-10 16:38 -0800
Re: update field with the same value Gene Wirchenko <genew@ocis.net> - 2011-02-11 12:05 -0800
Re: update field with the same value Erland Sommarskog <esquel@sommarskog.se> - 2011-02-11 08:54 +0000
Re: update field with the same value migurus <migurus@yahoo.com> - 2011-02-11 11:14 -0800
Re: update field with the same value Gene Wirchenko <genew@ocis.net> - 2011-02-10 17:18 -0800
csiph-web