Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3597068
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T20:04:14+00:00 2026-05-18T20:04:14+00:00

I have a stored proc that should conditionally update a bunch of fields in

  • 0

I have a stored proc that should conditionally update a bunch of fields in the same table. Conditionally, because for each field I also pass a “dirty” flag and a field should be updated only if flag is set to 1.

So I’m going to do the following:

create proc update 
@field1 nvarchar(1000), @field1Dirty bit, ...other fields...
as 
begin
    update mytable
    set field1 = case when @field1dirty = 1 then @field1 else field1 end,
    ... same for other fields
end 
go

Question – is SQL Server (2008) smart enough to not physically update a field if it’s been assigned its own value, like in case if @field1dirty = 0?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T20:04:15+00:00Added an answer on May 18, 2026 at 8:04 pm
    Question - is SQL Server (2008) smart enough to not physically update
    

    a field if it’s been assigned its own
    value, like in case if @field1dirty =
    0?

    No you should add a where clause that says…where field <> the value you are updating to.

    This doesn’t seem like a big deal at first, but in truth it can create a massive amount of overhead. One example, think about triggers. If that updates every field in the table, that trigger will fire for every row. YIKES, that’s a lot of code execution that’s needless, especially if that code is say, moving updates rows to a logging table. I’m sure you get the idea.

    Remember, you’re updating the field, it just happens to be the same value it was before. It’s actually good that this happens, because that means that you can still count the field as modified (think timestamp etc.). If it didn’t think updating the field to the same value was modifying the row, you wouldn’t know if someone inadvertently (or deliberately) tried to change data.

    Update due to comments:
    Link to the coalesce function

    Example:
    For handling null parameter values in your stored procedure

    Update Table SET My_Field = COALESCE(@Variable, My_Field)
    

    This doesn’t get around what I was talking about before with the field being updated to the same value, but it does allow you to check parameter and conditionally update the field.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a stored proc that should conditionally update a bunch of fields in
I have a quick linq question. I have a stored proc that should return
I have a stored proc on sql server 2008 that excepts a int parameter.
I have a stored proc with the basic layout below that returns a sys_refcursor
I have a WCF service method that calls a SQL stored proc. I'm developing
I have a stored proc, SP1, which executes and does select on one table.
i have a .NET page that will perform calculation by calling a stored proc
I have a stored procedure that does some parameter validation and should fail and
I have a stored proc that takes an input of xml value like this:
I have several listboxes that get each of their data from a separate stored

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.