Manage logins

A login account must be added to the Microsoft SQL Server before a user can access a SQL Server. By default, only members of the sysadmin and securityadmin server roles can add SQL Server logins. Logins are managed using SQL Server Management Studio.

Note: Creating individual login accounts for each user is not required if Windows authentication mode is used in SQL Server. You can map Windows user accounts and groups to SQL Server logins using the SQL Server Management Studio. For more information, see Add a user to a role.

A member of the sysadmin server role can add logins and configure certain login options, such as a username (login ID), password, a default database, and a default language. If the user is not assigned a username in the default database, the user's login name is used.

In addition to the default Microsoft SQL Server logins, four more default logins are created during AVEVA Historian installation: aaAdmin, aadbo, aaPower, and aaUser.

If a large number of users will be connecting to the database with the same set of permissions, creating a single database role to grant access for all of these users will reduce the work involved in account management. The individual users can then be added to the database role. For more information, see your Microsoft documentation.

Four Windows security groups are created when you install the Historian:

• aaAdministrators

• aaPowerUsers

• aaReplicationUsers

• aaUsers

These groups are mapped to SQL Server database roles of the same name. You can assign different levels of capability to users by adding the users to the Windows groups.

For more information about default AVEVA Historian logins and Windows security groups, see About security.

If you are a member of the sysadmin server role, you can add, modify, and remove logins, as well as administer database roles. For detailed information on managing logins, see your Microsoft documentation.