SQL Server security

Because the AVEVA Historian works closely with Microsoft SQL Server, it uses and takes advantage of the security features that Microsoft SQL Server has to offer. The purpose of security for a SQL Server is to control who can access the server, access specific databases within a server, and perform certain actions within a database.

A database user must pass through two stages of security for the Historian:

• Authentication, which validates the user’s identity to the server itself.

• Database authorization, which controls the database(s) that user can access, as well as the types of actions that the user can perform on objects within the database.

User authentication and database authorization are managed from Microsoft SQL Server Management Studio.

To access information in the AVEVA Historian databases, users need to be granted access to the databases. The Historian is shipped with preconfigured database roles and user accounts to serve as a starting point for your security model. Database roles, SQL Server login IDs, and user accounts are managed using the Microsoft SQL Server Management Studio.