This article contains information for On-Premise accounts. If your account is
hosted in the cloud, this article is not applicable.
This article is intended for those who host their own database and use SQL authentication.
- Open SQL Management Studio.
- Click the plus (+) sign next to Security to expand the Security folder.
- Click the plus (+) sign next to Logins to expand the Logins folder.
- Right-click on Logins and select New Login. The Login - New screen opens.
- Enter the login name (i.e. first initial, last name = JSMITH) into the Login name field.
- Select the SQL Server authentication radio button.
- Enter the password that matches your SQL password policy into the Password and Confirm password fields. If you don't have a password policy, uncheck the Enforce password policy check box.
- Click User Mapping on the left side of the screen, and locate the name of your Enterprise database within the list.
- Check the Map check box.
- Verify that Public and EBMSUser are checked in the Database Role Membership for the database.
- Click OK.
- Return to Enterprise Software and create a new user to match the SQL login that you created.
Comments
5 comments
We have migrated to a new server. I am unable to create usiadmin to the security logins to map to restored database as it says user already exists
0 upvotes
HI Theresa,
You need to delete the user from within the DB Security itself, then add it under the Security folder at the Server level, then enable it on the DB.
Shout if you need help.
1 upvotes
Hi Theresa, just poking my head in to second Sean's answer. Thanks!
0 upvotes
Thanks guys, I had done that but it would still not map. I found a script to do it
ALTER USER <user_name> WITH Login = <login_name>;
0 upvotes
The process I have always used is to create the login (at server level) without mapping to the database.
Then run this to fix/attach to the db user;
sp_change_users_login 'AutoFix', 'usiadmin'
0 upvotes
Please sign in to leave a comment.