Thanks Joie for replying.
I am slightly confused with your explaination of __$Operation = 3.
The following article says:
1 = delete
2 = insert
3 = update (old values)Column data has row values before executing the update statement.
4 = update (new values)Column data has row values after executing the update statement.
http://technet.microsoft.com/en-us/library/bb500305.aspx
Based on the above explaination of various operation statuses and the fact that the column in the original table is not nullable.
It is suprising that
a)I will see a record getting deleted with AuditTrackerUserID = NULL when infact based on table definition a null in this column is not possible.
b)I don't see any records with __$Operation =2 and AuditTrackerUserID being NULL. therefore I am assuming that the entry for inserted records is fine i.e. the value in the concerned column is not null. In such a scenario where inserted records are correct then how come the value in this column before the update became NULL.
Again, I appreciate you trying to help me out here, but this behaviour is driving me crazy.
More over I see such records only on production. I can't reproduce this behaviour on either developement or QC environment.