This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 24%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
I restored my production database "DB1" in development server. The database contains 'db_user' schema.
Same 'db_user' name i am using prod and dev.
After restoration, when 'db_users' trying to connect db, getting error "The Database DB1 is not accessible".
Also i checked in errorlog "Login failed for user 'db_user'. Reason: Failed to open the explicitly specified database 'DB1'. [CLIENT: <local machine>]"
i am getting error, when tried to grant access,
Same 'db_user' name i am using prod and dev.
May the same name, but different SID's and that one is important. So you have an "orphaned user", a database user without a login matching by the SID.
=> Troubleshoot orphaned users (SQL Server)
Thanks a lot for info,
since the same user already available, new sid has been created for the same user while restoring.
So I executed below statement in user db [DB01]
use [DB01];
alter user db_user with
login = db_user
Now user can access the DB01.
If you are going to make repeated restores, you can avoid having to this every time by creating the logins using the WITH SID option. That is
CREATE LOGIN db_user WITH SID = 0x....
You would take the SID from the other server.
Additional to Erland, you can generate script for the SQL login, see MS Support
Transfer logins and passwords between instances of SQL Server