Incorrect "changed by" login name

We work in a "shared database" environment. We implemented a database to capture change logs and the number of "Unknown" has diminished.

What I am more concerned about is running across a few instances where the login indicated in Source Control's "changed by" column isn't the developer who made the change.

Has anyone else run across this issue? If so, have you had any success finding the cause?
Tagged:

Comments

  • kkam99518kkam99518 Posts: 7 Bronze 2
    I think I may have solved our mystery....

    1) Developer A (running Source Control) alters object, does not commit

    2) Developer B (not running Source Control OR for some reason Source Control not logging) alters the same object

    3) Developer ? commits changes. The current version of the object does get saved to SCtrl BUT RedGate Source Control reports "last changed by" which is Developer A.

    Anyone else have a theory?
  • Hi kkam99518,

    Thanks for the update!

    We're going to pass this on to the developers to get their opinion as well and will come back to you if we have anything else to add.

    In the meantime if other community members have suggestions, don't be shy!
  • Sergio RSergio R Posts: 578 Rose Gold 5
    Hi,

    SQL Source Control uses the default trace to determine who last changed the object.

    I would also strongly recommend using the object locking feature when using the shared model to prevent issues:
    http://documentation.red-gate.com/display/SOC5/Lock+an+object
    Sergio
    Product Support Engineer
    Redgate Software Ltd
    Please see our Help Center for detailed guides on how to use our tools
Sign In or Register to comment.