title: SQL Login created but not mapped - user already exists - is there any connection between?
body: <p><em>Greetings,</em></p>
  
  <p>When I login into a particular MSSQL database as sa I see the following: somebody moved a database from server A to server B using <strong>restore option</strong>. I can see all the users in place (restored along with the database) - great. There are logins previously created on server A - great. All of those logins have <strong>sysadmin</strong> role. I think there's one problem - I don't see any <strong>mappings done between logins and users</strong> on server B (currently I have no access to Server A so I can't look at the configuration).</p>
  
  <ol>
  <li>According to <strong>security properties</strong> - all of those 'local' database users are '<strong>SQL user without login</strong>' - but I'm sure a proper application uses those users on a regular basis and there are configuration files where passwords are stored.</li>
  </ol>
  
  <p><strong>Question #1</strong> - if there's a login with sysadmin role and there's a local database user of the same name (as login) - does the application use login or local db user in order to work properly? (there's no mapping between the two)</p>
  
  <p><strong>Question #2</strong> - should mapping be done between all the logins and corresponding database users when moved from one server to another? At the moment there isn't any mapping done and my cooworkers are using logins with sysadmin role to access whole database.  </p>
  
  <p><em>Regards,</em></p>