SQL Server 2016 SP2 on Windows Server 2016
I have a client that is using temporal tables for data auditing and session contexts to secure data from different systems from one another.
To access any data you first have to set the context variable like so.
13 of the most used tables have temporal versioning so they can audit data.
The server has 2 cores with 8 GB memory.
My issue is that the server is not used very heavily but the CPU and IO are always high. My thought is that it could be from the things I mentioned above but can't find articles to confirm or deny this.
Has anyone used these features and if so, what kind of overhead did it cause?
Thank you!
To access any data you first have to set the context variable like so.
exec sp_set_session_context @key = 'SystemID', @value='A65T' 13 of the most used tables have temporal versioning so they can audit data.
The server has 2 cores with 8 GB memory.
My issue is that the server is not used very heavily but the CPU and IO are always high. My thought is that it could be from the things I mentioned above but can't find articles to confirm or deny this.
Has anyone used these features and if so, what kind of overhead did it cause?
Thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
https://www.mssqltips.com/sqlservertip/4778/performance-impact-of-sql-server-2016-rowlevel-security/
Aside that and without knowing the specs for your database(s) tables/sizes - it looks to me that the hardware used that "has 2 cores with 8 GB memory"...is very low end for running a SQL Server. I mean my old Dell 790 desktop has more hardware resources than your SQL Server so I would through this into consideration as well.