Home > Archive > MS SQL Server security > July 2005 > Cleaning up hung groups and orphans in SQL 6.5









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Cleaning up hung groups and orphans in SQL 6.5
Norman Seymore

2005-07-08, 8:23 pm

I have a SQL 6.5 server that has orphans in the databases, and a hung group
(not a db group) that is visible in SSM (SQL Security Manager). While I still
don't fully understand why I cannot see (in enterprise manager or in the
system tables) the NT groups that have been added to SQL via SSM or
xp_grantlogin, the real problem is that this group that is visible in the SSM
GPF's the SSM when I tell it to revoke (remove) it. I don't know who added it
or when, but I would like to get rid of it. There are also a lot of orphaned
DBUsers and DBGroups, and DBUsers in the DB Public groups, from DBs being
restored to the server.

My end goal is to clean up the server as if it were just created, with the
option to retain specific SQL and NT Accounts that I need to keep (aside from
the ones that are added automatically, as in the Administrators, which I
obviously need to not touch).

One suggestion is to rebuild master then clean up the orphans in the
databases. I would prefer not to rebuild master. Is there an easier way to do
this? A utility or set of scripts that a 6.5 guru may know about?

TIA
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com