"Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
news:%23UtbPUvYDHA.2632@TK2MSFTNGP09.phx.gbl...
> Restoring a user database does not put back logins and what you quite
often
> see is Users in the database with a blank login name. This means they are
> orphaned.
> Logins are stored in master.
>
> I like this article
>
> http://support.microsoft.com/default.aspx?scid=KB;en-us;q246133
>
>
> Scripting the logins would work but they will still be orphaned.
>
> Have a look also at
>
> sp_change_users_login
>
> --
>
> ----------------------------
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
>
>
>
> "Bob Brainin" <brainin@btclick.com> wrote in message
> news:bhguk2$jne$1@hercules.btinternet.com...
> > I restored an early backup on SQL 7, only to find that users had been
> > dropped in EM. I then restored a later backup which I was sure had all
the
> > users properly authorised, but they're still not there!
> >
> > What is the correct way to administer this? Is it by ticking the
> individual
> > boxes for each table? Scripting? Setting it up in Master db and changing
> the
> > ODBC default?
> >
> > TIA
> >
> > Bob Brainin
> >
> >
>
>

"Bob Brainin" <brainin@btclick.com> wrote in message
news:bhguk2$jne$1@hercules.btinternet.com...
> I restored an early backup on SQL 7, only to find that users had been
> dropped in EM. I then restored a later backup which I was sure had all the
> users properly authorised, but they're still not there!
>
> What is the correct way to administer this? Is it by ticking the
individual
> boxes for each table? Scripting? Setting it up in Master db and changing
the
> ODBC default?
>
> TIA
>
> Bob Brainin
>
>