Re: Windows security

From: Awais Bin Khalid (AwaisBinKhalid_at_discussions.microsoft.com)
Date: 07/24/05 

Date: Sun, 24 Jul 2005 13:40:03 -0700

Every database contains a table called sysusers, which stores a list of all
users who have access to that database. You can use following stored
procedures to get detailed info and put same users on different databases.

sp_change_users_login : Use this stored procedure to see and fix orphaned
users.

sp_validatelogins : This stored procedure reports information about orphaned
Microsoft Windows NT/2000 users and groups that no longer exist in the
Windows NT environment but still have entries in the Microsoft SQL Server
system tables.

Detail on following links:
http://vyaskn.tripod.com/troubleshooting_orphan_users.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133

Hope this helps.

Awais Bin Khalid
Microsoft Certifiec Application Developer
www.xavor.com

"Uri Dimant" wrote:

> Hi
> There are two stored procedures provided by Microsoft to transfer
> users/logins with their original SID.
> Please do searching on the internet
>
>
> If you login has an appropriate (a login should be created on remote
> server)permissions perform a backup to another computer
> BACKUP DATABASE DataBaseTO DISK =
> N'\\Server\backup\Database.BAK'
>
>
> "pmcguire" <pmcguire@discussions.microsoft.com> wrote in message
> news:165C4A5A-8D38-4850-8C7A-7805B98D8A46@microsoft.com...
> > I have 2 SQL servers (SQL1 and SQL2) residing on two Windows servers (Win1
> > and Win2). I want to back up a database (mydbase) from SQL1 and restore
> it
> > to SQL2. I am using Windows authentication, and I would LIKE to be able
> to
> > do this without rebuilding the User list every time.
> >
> > For example, I want mydbowner to have db_owner rights on mydbase on both
> > SQL1 and SQL2; Win1/mydbowner and Win2/mydbowner logins exist already,
> and
> > Win1/mydbowner already has db_owner privileges to SQL1.mydbase. When I
> > backup and restore, Win1/mydbowner exists as a user on SQL2.mydbase, but
> of
> > course the login doesn't exist on SQL2.
> >
> > I guess what I would like to be able to do is create the user
> Win2/mydbowner
> > (and grant it db_owner privileges) on SQL1.mydbase without creating the
> login
> > on SQL1. Can this be done?
> > --
> > Pat
>
>
>

Relevant Pages

  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Database Connectivity
    ... But, MSDE has been know to work very reliably in small user LANS, ... > just a simple step to attach the tables from MSDE to SQL Server. ... database, or pay for an "industrial-strength" version of it when there ... Don't like Microsoft?, sounds like a personal problem to me. ...
    (comp.lang.python)
  • Performance optimization vs satisficing (was Language Oriented Programming)
    ... >machines that were too small. ... Microsoft has been a leading offender here. ... >arcane issue for server engines. ... magnitude slower, yes, I recall working on a 200mb database, trying to ...
    (comp.object)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Repairing / modyfing Exchange
    ... Customer Service and Support for more immediate assistance. ... This service gives you access to Microsoft technical support engineers who ... database by using the old Server's database files, ... >> up with the First Storage Group, so you would like to delete it and then ...
    (microsoft.public.windows.server.sbs)