The Last Changed By column shows the last user to alter an object.
SQL Source Control gets the Last Changed By information from the default trace, and will store the details in tempdb by default.
If the column shows Unknown instead of a username, the documentation here lists possible causes.
Of the causes listed, lack of permissions to the default trace and/or tempdb are the most common. Either case will result in the warning, "SQL Source Control uses the default trace to work out which user made which change. You don't have the correct permissions to access the default trace, so the information isn't available."
If you see this warning, make sure that the user has:
- ALTER TRACE and VIEW SERVER STATE permissions to access the default trace.
GRANT ALTER TRACE TO user
GRANT VIEW SERVER STATE TO user
- EXECUTE and ALTER permissions on tempdb
use tempdb
GRANT EXECUTE TO user
GRANT ALTER TO user
Note: If granting access to tempdb is not possible, you can configure SQL Source Control to use a custom Changelog database instead.
If the problem persists and you have a supported license, please enable logging and send your log files in %localappdata%\Red Gate\Logs to support@red-gate.com.
Was this article helpful?
Articles in this section
- The process cannot access the file 'C:\Users\*******\AppData\Local\Red Gate\SQL Source Control 7\Caches
- Duplicate definition troubleshooting in SQL Source Control
- The target principal name is incorrect
- SQL Source Control can't access this database - make sure the database is online and you have permission to access it
- Meanings of the colored dots in the SSMS Object Explorer for SQL Source Control
- Last Changed By column shows Unknown
- How to Link SQL Source Control to TFS
- How to link to an existing SVN repository
- GIT Push/Pull greyed out
- Objects changed by unknown