Change Tracking

  • Sweet!

    +1

    Not all gray hairs are Dinosaurs!

  • Had to guess. Reasoned that change tracking would require a PK. How else would you know what was changed? Thanks for the question.

    [font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
    Connect to me on LinkedIn

  • Good question...

    learn something new today 🙂

    _______________________________________________________________
    To get quick answer follow this link:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

  • Nice question, thanks.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Nice question. The idea that one can track changes to a table without some way of identifying a row which is changed is quite bizarre, particularly since SQL tables can contain duplicates, so it seems natural to require a primary key. For that reason I find it hard to understand why I got two points for answering this, instead of just one, but as points don't matter anyway I don't actually care.

    Tom

  • Good question. 🙂

  • Thanks for the question.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • I don't have "ChangeTrackingDemo" database on my server, so it will give error for both the statements.

    Please mention the considerations properly.

Viewing 8 posts - 16 through 22 (of 22 total)

You must be logged in to reply to this topic. Login to reply