Which feature is not part of SQL Server Security with Historian Server?

The feature that is not part of SQL Server Security with the Historian Server is that it manages physical hardware resources. SQL Server Security primarily focuses on ensuring that only authorized users can access databases and perform permissible actions, thereby safeguarding data integrity and confidentiality.

Access control to specific databases allows database administrators to set permissions and restrict access based on user roles, which is crucial for maintaining data security. User authentication is essential, as it verifies the identity of users attempting to connect to the Historian Server, ensuring that only authenticated personnel can access sensitive information.

Additionally, controlling actions within a database involves defining what specific tasks users can perform, such as reading, writing, or modifying data, which aligns with fundamental security practices to prevent unauthorized changes.

In contrast, managing physical hardware resources pertains more to system administration and infrastructure management rather than security. This process is not the function of SQL Server Security, which is specifically designed to protect data from unauthorized access and manipulation.