Setting up a user

  1. Start one of the Microsoft applications mentioned above. Ensure that you sign in as a system administrator.
  2. Specify these lines. You can specify this information for each user and then run the script collectively. 
    sp_addlogin  '<login_name>', '<password>'
go
use <database>
go
sp_adduser '<login_name>', '<user_name>'
go

    Where:

    • <login_name> is the sign in name for the user.
    • <password> is the password.
    • <database> is the name of the production database.
    • <user_name> is the name of the user associated with this sign in name and database. If a user name is not specified, the user name defaults to the sign in name.
    Some CPM components may not work successfully unless the sign-in name matches the user name exactly. For example, to create a user Scott with a sign-in of Scott and a password of password on database CTRAIN, you must specify: 
    sp_addlogin 'Scott', 'password'
go
use CTRAIN
go
sp_adduser 'Scott'
go
  3. Run the query.
  4. Verify that the commands were run successfully.
  5. An administrative user requires access to both the production and authorized databases to sign in to the Architect. If you are creating an administrative user, specify these lines: 
    go
use <database>
go
sp_adduser '<login name>', '<user name>'
go

    For example: 

    go
use CTRAIN_A
go
sp_adduser 'Scott'
go
  6. Run the query.
  7. Verify that the commands were run successfully.

    For more information and options regarding security and interfaces, see the Microsoft SQL Server documentation.