On a shared model, the Changed By column says unknown for some uncomitted changes on the Commit List
When I try to commit changes it says unknown user. I believe it is very important to be able to track who's making what changes.
In v3.1, we store user information when an object changes so you don’t see “unknown” on the commit list for changes on a shared model. Details are at https://documentation.red-gate.com/display/SOC32/Logging+changes+to+shared+databases
-
If your default trace rolls over a lot and you are always seeing "unknowns," then you could try 2 things:
1) Change your polling options so the blue indicators are less frequent. This would create less entries in the Default Trace. There are instructions on how to do this at http://www.red-gate.com/messageboard/viewtopic.php?t=12837. Each user would need to do this since these settings are a per user (per machine) option.
2) Close SSMS more frequently. Polling will continue to happen for every db under source control that you touch in a session and will not stop until SSMS is closed. Therefore, if you are no longer actively working against the db, you may want to close SSMS.
Keep voting here if we should implement our own trace so "unknown" isn't shown as often. If implemented, this is something you could opt-in to. Let us know how you would feel about having an additional trace on your development db servers.
-
On a shared model, in the commit list or undo dialog, we get the "changed by" information from SQL Server's default trace. There are some cases where we can not get this information:
- Users or roles
- Dropped objects
- If you don't have access to the default trace
- If the default trace is turned off
- If the default trace no longer contains the information because it has rolled over (this is probably the case the first time you link an existing database)
- SQL 2000 databases also do not have a default trace (Note: We do not support SQL 2000 databases, http://www.red-gate.com/products/sql-development/sql-source-control/requirements)Even though "unknown" is shown on the commit list, we always record who commits the object so the history will never show unknown.
We are looking at implementing our own trace to help identify these "unknown" situations. Keep voting/commenting here if you would like this.