Re: Cannot Drop Users

Zekske (Zekske@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I attached databases from a SQL7.0 server in domain A on a SQL 2000 server
in domain B.
When I try to drop de database users with the sp_dropuser command I get
the message user does not exists.
Strange thing is that when I execute sp_helpuser I can see the users but
when I execute SP_Change_users_login 'report', there not listed.
Those users are domainusers.

I think you should use sp_revokedbaccess for domain users, rather
than sp_dropuser.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.

Relevant Pages

  • Re: Output stored procedure
    ... but the .execute command doen't show teh records. ... What object window? ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ... Books Online for SQL Server 2005 at ...
    (comp.databases.ms-sqlserver)
  • Re: grant access to extended properties
    ... Do you know anything about this "EXECUTE AS" for 2000? ... I played around with GRANT but apparently, a member of "db_datareader" ... Reading Books Online tells us that to add extended properties, ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: Syntax Check
    ... If you're running against SQL Server, you can use "SET PARSEONLY ON|OFF". ... Check out books online for details on PARSEONLY. ... and generates an error if there is a syntax error, ... execute something for real. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: AD groups and auditing
    ... EXECUTE AS should be manageable, provided that the original login is ... SQL Server is made by a proxy user that impersonates the actual user ... Books Online for SQL Server 2005 at ...
    (microsoft.public.sqlserver.security)
  • Re: Scheduled Job Fails with Error: "Login Failed for "sa"
    ... The strange thing is we can ... execute the package successfully but we just can't run it ... Somewhere in your package ... We also verifyied the SQL Server Agent ...
    (microsoft.public.sqlserver.dts)