Login problem after DB restore
From: Mary (Mary_Scheffler_at_urscorp.com)
Date: 03/10/04
- Next message: giovanni: "Re: SQL7 standalone"
- Previous message: Dean Nates: "Re: Duplicate Identical ROWs PROBLEM in table with unique Clustered Index"
- In reply to: Don: "Login problem after DB restore"
- Next in thread: jayzee_jz20032_at_hotmail.com: "Re: Login problem after DB restore"
- Reply: jayzee_jz20032_at_hotmail.com: "Re: Login problem after DB restore"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 10 Mar 2004 10:15:38 -0800
Don, we just went through the same scenario here at my
office. The problem when moving a database from one
server to another, is the SID doesn't match between the
master and user database. Refer to Microsofts Knowledge
Base Articles, 240872, 168001, 298897. We also had a
problem when we changed the IP address and name of the
server. If you need information on this, refer to
http://ambrosoli.com/ambrosoli/how_to_rename_a_sql_server_7
_0.htm
>-----Original Message-----
>SQL 7.0 using SQL/Windows authenication.
>
>A DB backup was restored from one server to another which
>had a new install of SQL 7.0.
>
>Problem:
>In EM/Security, if I try to add the user login 'xxx' with
>access to the restored DB, SQL says the login name
>already exists in the the DB. Yet, it doesn't exist, that
>I can see any where. If I try to access the DB from an
>ODBC connection using the login 'xxx' it denies access.
>I tried droplogin 'xxx', but that didn't help.
>Any ideas?
>Thanks,
>Don
>
>.
>
- Next message: giovanni: "Re: SQL7 standalone"
- Previous message: Dean Nates: "Re: Duplicate Identical ROWs PROBLEM in table with unique Clustered Index"
- In reply to: Don: "Login problem after DB restore"
- Next in thread: jayzee_jz20032_at_hotmail.com: "Re: Login problem after DB restore"
- Reply: jayzee_jz20032_at_hotmail.com: "Re: Login problem after DB restore"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|