Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 restoring a database to a new server

Author  Topic 

priyaram
Yak Posting Veteran

82 Posts

Posted - 2007-02-01 : 09:17:56
suppose we are restoring the database to a new server, the logins are getting created.
So when an user want to login to this new database , what ever he used before to getinto that database should have to use the same password.??

So when we restore a database only, tables , logins are created, or what are the other things getting craeted like stored proc, jobs???

thanks in advance

Kristen
Test

22859 Posts

Posted - 2007-02-01 : 09:28:42
"should have to use the same password.??"

Nope.

Logins are at a server level.

Access, for a given login, is at a database level.

So if you take a backup of a database on Server One, and restore it to Server Two, then the User Access is in the database on Server Two, but the Logins aren't there on Server Two itself.

You need to script the logins off Server One and create them on Server Two.

Or you can generate Missing Logins once you have restore the database on Server Two - but their passwords will be lost.

This link is probably out of date (refers to SQL 2000), but I'm pretty sure a solution for 2005 came up in the last couple of days, so would be worth doing a search.

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=55210&SearchTerms=Fix%20Orphaned%20Users,Scripting+users,logins+from+one_server+to+another

Kristen
Go to Top of Page

priyaram
Yak Posting Veteran

82 Posts

Posted - 2007-02-01 : 09:33:22
when i restore , all the logins are got created.Once i create them at the server level, what's the password they have to use at the database level.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-02-01 : 10:35:13
The password is stored at the Server level, not at the Database level (unless something has changed in this regard in SQL 2005)

Kristen
Go to Top of Page
   

- Advertisement -