AVEVA Historian default logins
- Last UpdatedFeb 27, 2025
- 1 minute read
When the AVEVA Historian is installed, default SQL Server logins are created that you can use for logging on to the Historian from client applications. These default logins provide "out of the box" functionality in that you do not have to create logins to start using the system. The following table describes the pre-configured logins:
|
Login Name |
Description |
|---|---|
|
aaAdmin |
A user who can access and modify all data and create objects. Cannot drop the database or truncate tables. |
|
aaPower |
A user with full read access and the ability to create objects and modify the contents of the non-core tables. |
|
aaUser |
A read-only user who can access all data, but cannot modify data or consume database resources. |
|
aadbo |
Database owner. Full permissions. |
The default database for each of these logins is the Historian Runtime database. This default security model is provided as a starting point for system security and is suitable for many types of installations.
These logins are valid if the Microsoft SQL Server is set to mixed mode security. If only Windows authentication is used, you must configure the access rights for each user.
Important: Never use blank passwords for logins.
The following logins are provided for backward compatibility only. They will be deprecated in a future release. Do not use these logins.
|
Login Name |
Description |
|---|---|
|
wwUser |
Same as aaUser. |
|
wwPower |
Same as aaPower. |
|
wwAdmin |
Same as aaAdmin. |
|
wwdbo |
Same as aadbo. |