November 29, 2011 at 9:50 am
hi,
Has anybody had a similar problem to the following. We have a VB6 application where users initially connection to SQL Server using Integrated Security. The application then switches on an application role to give the user the required permissions in the database.
What we've seen happen over the past few days for a small number of users (not all) is that once the approle has been switched on, the user has connected to the database with a SQL Login (one that exists in the database). So, basically, if we set up a trace you see the 'SQL:BatchStarting' event for the sp_setapprole with a login name of 'Domain\username' (i.e. integrated security) but the 'SQL:BatchCompleted' event of the sp_setapprole has a LoginName which is a SQL Server login.
We have connection pooling switched off in the connection strings.
This is only happening with a very small number of users.
Has anybody experienced anything similar to this?
Thanks,
SJB
November 29, 2011 at 10:58 pm
Is it consistently the same SQL Server login? Is there anything special about that login? For instance, is it the owner of the app role?
K. Brian Kelley
@kbriankelley
November 30, 2011 at 9:58 am
Hi Brian,
Thanks for the reply.
Yes, it is consistently the same login and no there isn't anything special about the login - it's not the owner of the app role.
It's funny that in most cases there isn't an issue - users connect with there Windows login once the app role has been switched on.
We're going to get the AD account recreated to see if there is anything odd about the account which could be causing the issue.
Cheers,
SJB
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply