EXCELLENT. That gave me exactly what I needed. Vended solution services somehow set up inside of SQL Server.

Now I just need to figure out how to fix the problem, which...

Big shop or small shop?

I was just reflecting this morning that the employer I currently work for has both. One small unit that has its own collection of  DBAs, about...

• This reply was modified 7 months ago by  Brandie Tarvin.

That did not come up in Google. I just looked at it, and the principal ID for all lines is dbo, not the SQL login in question.

Is "name" in that...

And now the non-obsolete version that appears to work as well (possibly better?).

$IPAddys = Import-Csv C:\TEMP\FailedSQLLoginSearch_AllSvrs.csv | Select-Object -Property ServerName, LoginName, HostName -Unique 
$results=@()
Foreach ($ips in $IPAddys)
{
...

WHOO HOO! Figured it out. Needed to throw a hash table in there...

Thank you, Frederico. Without your code I never would have reached this. Now I'm just fiddling with user-friendly...

Frederico, the expressions line you gave me isn't working for me. The information writing to the screen is " is unreachable." as if $n.NAME is null or empty and the...

• This reply was modified 7 months, 3 weeks ago by  Brandie Tarvin.

At the moment, configuring extended events is not something I can do. We need to jump through hoops to make changes to production servers and this is a high priority...

• This reply was modified 7 months, 3 weeks ago by  Brandie Tarvin.

Yes, I was messing around and forgot to change xlxs to csv.

Oddly, I'm not getting a file created with your posted suggestion. I'm going to noodle around a little more...

Sigh. I wish I could take comfort in "Your emergency is not my emergency." Sadly, my job makes other people's emergencies my emergency.

Any powershell gurus around? I'm still in my...

YAY! WITH EXECUTE AS OWNER solved my issue. No extra permissions required, no impersonation permission granted to the user group. Thank you all so much! I appreciate you.

AOR = Area of Responsibility. Think of it like departments or smaller chunks of a business division. I am separating out their jobs from the jobs owned by the DBAs...

OKAY. Now the WITH EXECUTE AS <user> / OWNER is the syntax I could not for the life of me find. I might try that.

The security is being implemented across...

Another approach would be to sign the stored procedure and create a certificate user in MSDB with appropriate permissions. It can get a bit involved but the following may...

One approach I can think of to this is to have the end users insert their job request into a table. Then you have a SQL job that runs...

Sadly, without giving IMPERSONATE to the users, I cannot let them...