Aug 05, 2019 09:38 AM|PatriceSc|LINK
Windows authentication just ensures the current Windows account is used to connect to SQL Server. In a web app, this is is moft often the account under which the application runs. To get the user information on the SQL Server side you would need to enable
also user impersonation so that each db connection is done using the user identity (but AFAIK it will create a connection pool for each user)
My personal preference is to do that when really needed (ie using SQL Server side permissions for example). Here I would likely just pass the user name or id explicitely as an entity property (possibly generalized through some interface or whatever).
Edit: this is to keep track of who have created/changed each row and when ?