Forum Replies Created

Viewing 15 posts - 2,161 through 2,175 (of 6,036 total)

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/7/2012)


    Try this:

    ....

    I don't think it proves anything.

    Logical/physical reads/writes are about pages read/written.

    There was never an argument that SQL Server finds pages affected by the UPDATE not changed and...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/7/2012)


    I have said, over and over again, that I don't know whether the in-memory page is written to or not. A page that is exactly the...

  • RE: UPDATE when the values are the same

    MissTippsInOz (9/7/2012)

    You have had numerous genuine responses from people who are trying to help you to understand the behaviour of a 'non-updating update'. You have been given code (and...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/7/2012)


    A modification counter used by statistics update is increased, yes. Rolled-back changes, and changes that don't change anything all count.

    Key word - changes.

    No matter if it's rolled...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/7/2012)


    If you don't stop being snarky in your replies

    You may notice I just quoted you. Word to word.

    And that is exactly the problem. My question to...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)


    Statistics updates are triggered when a modification threshold is exceeded. The modification counters count logical changes - even rolled back changes count.

    So, there are modifications?

    SQL...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)

    The logical update operation.

    What exactly is logical update operation and what other kind of update operatios are there?

    If you don't stop being snarky in your replies

    You may...

  • RE: UPDATE when the values are the same

    Sergiy (9/6/2012)


    SQL Kiwi (9/6/2012)


    No idea, actually. Perhaps it's just simpler to always take an exclusive lock prior to possibly changing data. Perhaps it wouldn't be safe to allow...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)


    Sergiy (9/6/2012)


    Used for data-modification operations, such as INSERT, UPDATE, or DELETE. Ensures that multiple updates cannot be made to the same resource at the same time.

    I thought you...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)


    No idea, actually. Perhaps it's just simpler to always take an exclusive lock prior to possibly changing data. Perhaps it wouldn't be safe to allow people...

  • RE: UPDATE when the values are the same

    I've come accross a very ineresting thing.

    I was trying to test for some other case, but the original test geve me some different result.

    I was running this:

    BEGIN TRANSACTION

    UPDATE dbo.test

    SET...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)


    Sergiy (9/6/2012)


    SQL Kiwi (9/6/2012)


    Taking a shared lock would not give the same behaviour as taking an exclusive lock.

    Can you bring sopme details please?

    The two lock types are different,...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)


    What do you mean by this?

    By updating you're losing data.

    You might think you don't need it anymore, but still - you're losing data previosly recorded in the database.

    Which...

  • RE: UPDATE when the values are the same

    SQL Kiwi (9/6/2012)


    Taking a shared lock would not give the same behaviour as taking an exclusive lock.

    Can you bring sopme details please?

  • RE: UPDATE when the values are the same

    Eugene Elutin (8/29/2012)

    I would probably agree on that with one small addition: such verification should be made in a client app not in the update statement itself, otherwise you may...

Viewing 15 posts - 2,161 through 2,175 (of 6,036 total)