Thanks Ninja, but we're not even getting close to a DB yet.

Our prod SQL Server can't get info for the new name, let alone allow a login to proceed.

All...

More info:

1) For the user in question, a newname account was created as a copy of their oldname account, then deleted. Then along comes me and renames the oldname...

I should have noted that the users are in AD groups, and access the SQL Servers via their group memberships.

Renaming the users accounts does not affect their group membership.

Moreover, it's...

Found it.

It works, although it doesn't appear to be faster than my current solution.

I'll keep at it...

P

dsquery doesn't appear to be supported on XP.

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2008, Windows Server 2008 R2

I get ...not...

The edict came from on high a couple of years ago: NO NEW SERVERS! (except when a prod box dies).

We grant SQL Server / DB access to Windows groups.

We determine which version of the app (read "Server"), which projects (read "databases") users can see, as well as what...

@opc.three: thanks. I can't wait for the time when we move on from XP :-), and I can begin using those AD cmdlets.

@bruce-2: thanks for that. I can see I''m...

Thanks Laerte!

Found you a couple of months ago, I appreciate your work.

I also found these functions last week.

P

I remember it well. Hilarious!

PS: Is your picture Robert Hays in Airplane?

Confirmed.

Set-Location SQLSERVER:\SQL\MyServer\Default\Databases\MyDB\StoredProcedures

dir | select name

does not return any system sprocs. I wonder why the repl sprocs would fall into the user category.

Weird...

P

$Srv = New-object Microsoft.SqlServer.Management.SMO.Server "Mufasa"

$Srv.Databases["Abb"].StoredProcedures | where {$_.issystemobject -eq $true} | select name

This returns 1300+ system procs -- including repls, and I don't have replication enabled.

P

This will exclude all non-user objects. I assume they're probably not required anyway.

Get-ChildItem | where {$_.IsSystemObject -eq $false}

Mystery solved. Ugh.

I managed to do what I wanted using Substring and IndexOf.

Thanks!