Based on the assumption that Windows stores some sort of (GUID?) value when
an application uses Impersonation to connect to a SQL Server database, is it
possible to obtain this value at either the application or database level?
My objective is to maintain an audit log of changes to application data,
including some form of unique user identification, despite the use of
Impersonation.
Any tips, links, etc. that address this are greatly appreciated.
TIA
Russell Fields - 24 Nov 2008 16:45 GMT
dj,
If the impersonation is done before you reach the SQL Server, then the SQL
Server does not know who you really were. Does the domain know?
If the impersonation is done inside SQL Server, you might find SQL Server
2005/2008 ORIGINAL_LOGIN() function useful.
You also might be interested in signing up and voting for this
recommendation on Microsoft Connect:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=238908
RLF
> Based on the assumption that Windows stores some sort of (GUID?) value
> when
[quoted text clipped - 8 lines]
> Any tips, links, etc. that address this are greatly appreciated.
> TIA