AVEVA Historian default users and roles
- Last UpdatedFeb 27, 2025
- 1 minute read
AVEVA Historian is shipped with a number of preconfigured user accounts and roles.
Note: During installation, Historian requires that you change the passwords for any default login accounts, such as wwUser. Use of default passwords (which are often published in various documents) is highly discouraged.
The following table describes the default SQL Server usernames, the login IDs and database roles to which they belong, and the actions that they are allowed to perform in the Runtime database. You can add additional users and roles using SQL Server Enterprise Manager.
|
Login ID |
Username in Database |
Member of Role |
Permissions |
|---|---|---|---|
|
aaUser |
aaUser |
aaUsers |
SELECT on all tables INSERT, UPDATE, DELETE on PrivateNameSpace and Annotation |
|
aaPower |
aaPower |
aaPowerUsers |
CREATE Table CREATE View CREATE Stored procedure CREATE Default CREATE Rule SELECT on all tables INSERT, UPDATE, DELETE on grouping tables |
|
aaAdmin |
aaAdmin |
aaAdministrators |
CREATE Table CREATE View CREATE Stored procedure CREATE Default CREATE Rule DUMP Database DUMP Transaction SELECT, INSERT, UPDATE, DELETE on all tables |
|
aadbo |
dbo |
db_owner |
Full database owner capabilities |
The following users and roles are provided for backward compatibility only. They will be deprecated in a future release. Do not use these users and roles.
|
Login ID |
Username in Database |
Member of Role |
Permissions |
|---|---|---|---|
|
wwUser |
wwUser |
wwUsers |
Same as for aaUser. |
|
wwPower |
wwPower |
wwPowerUsers |
Same as for aaPower. |
|
wwAdmin |
wwAdmin |
wwAdministrators |
Same as for aaAdmin. |
|
wwdbo |
wwdbo |
db_owner |
Same as for aadbo. |
Each default role contains the corresponding SQL Server user account, as well as the corresponding default Windows security group. For more information on the default Windows security groups, see Default Windows security groups.