You will probably want to create an overload versus changing that one method as there are a number of places that will not expect the parameter.  But past that, I see no issues.  Also, if the active session is the same as the logged-in user, then you could just add the additional logic without a new parm as well using the security userPK from within that method without the needs for parms:

Hi,

I am having audit log and data encryption in my database. I need to pass current login user name to a stored proc whenever that is any new connection opened. I was thinking to override SqlDataSourceItem.CreateBlankDbConnection() to add call for it.



Do you foresees any problem with this approach?



Thank you