Re: SQL Server 2005: Checking if Login is connected to any databas
- From: "Laurentiu Cristofor [MSFT]" <laur@xxxxxxxxxx>
- Date: Fri, 25 Aug 2006 14:55:07 -0700
No, there is no such stored procedure. There is no way to tell if a login
can be really dropped - there might be databases that refer to it that are
detached at the moment you do your check. Writing a procedure to check all
databases is the quickest way, but it will not cover the issue above.
Why do you want to make this check? I may be able to suggest a better
alternative if I understand what you are trying to accomplish.
Thanks
--
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sebitti" <sebittionline@xxxxxxxxxxxxxxxxx> wrote in message
news:EB9F9ACB-35EC-4C77-A027-2B84AE95F444@xxxxxxxxxxxxxxxx
Hi,
SQL Server 2005 allows dropping login that has mapped users in database. I
need a way to check if login is mapped to any database before I call
sp_droplogin. Is there any stored procedure that does this check?
BR
Johanna Turku
"Uri Dimant" wrote:
Hi
BOL says
A login cannot be dropped while it is logged in. A login that owns any
securable, server-level object, or SQL Server Agent job cannot be
dropped.
You can drop a login to which database users are mapped; however, this
will
create orphaned users. For more information, see Troubleshooting Orphaned
Users.
select * from sys.server_principals
select * from sys.database_principals
select * from sys.user_token
"Sebitti" <sebittionline@xxxxxxxxxxxxxxxxx> wrote in message
news:0AE8D1C4-165B-4115-A2DA-63F0A64C4AC8@xxxxxxxxxxxxxxxx
Hi,
We have an application that allows users to add and drop logins. In Sql
Server 2000 it was not allowed to drop a login that was linked in some
database but in 2005 this is allowed. We need a way to check if login
can
really be dropped.
What is the best way to check if a login is linked to any database? Any
stored procedure that does this check? Only way I can think of is to
list
all
databases and check their users one by one... i hope there is a quicker
way
to do this.
BR
Johanna Turku
.
- Follow-Ups:
- References:
- Re: SQL Server 2005: Checking if Login is connected to any database
- From: Uri Dimant
- Re: SQL Server 2005: Checking if Login is connected to any database
- Prev by Date: Re: SQL2005 grant user access to certain tables
- Next by Date: Re: SQL2005 grant user access to certain tables
- Previous by thread: Re: SQL Server 2005: Checking if Login is connected to any database
- Next by thread: Re: SQL Server 2005: Checking if Login is connected to any databas
- Index(es):
Relevant Pages
|
|