0

I'm trying to use SQL Server Profiler to Replay a Trace.

But when it tried to impersonate the users/logins, it gives this error:

Failed to set proper user name ('application_login') for the connection

So, I ran the following, from the RDS instance's "master" login:

USE [master];
GRANT IMPERSONATE ON LOGIN::[application_login] TO [profiler_login]; 

But I get the following error message:

Msg 15151, Level 16, State 1, Line 52 Cannot find the login 'application_login', because it does not exist or you do not have permission.

I can successfully grant impersonate at the user level, but it doesn't resolve the initial issue in SQL Server Profiler.


Is this a AWS RDS limitation? Is there a workaround? Am I doing something wrong?

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.