Search the Community
Showing results for tags 'sql server'.
Hello. I have ESMC v7.2.1266.0 running with Microsoft SQL Server 2017 (RT Express Edition (64-bit) v14.0.2027.2. I'm doing some maintenance in our environment and I see that SQL Server 2017 CU21 was released on 7/1/2020. The version I'm running (v14.0.2027.2) was released 7/9/2019. My question is am I able to upgrade our SQL to CU21 without causing any major issues with ESET? I believe it should be okay, but I wanted to see if anyone else has upgraded their DB or if the version of ESMC has be using SQL v14.0.2027.2. Thanks! https://support.microsoft.com/en-us/help/4047329 https
When our ESET ERA was in v5, the database name was called 'ESET' in our SQLEXPRESS instance (in SQL Server11.0.2100). This instance has other databases running. After our ERA was upgraded to v6, the new database was created 'era_db' in another SQL Server instance call ERASQL (in SQL Server 12.0.2000). This instance only has only one database running (era_db). So we have two SQL Server instances running in the same server, which takes up unnecessary CPU. Questions: 1. Is the ESET database in my SQLEXPRESS still in use or can I take it ofline? (the last eventlog date was the date i upgraded
Our resources monitor / performance tool for SQL Server indicating ESET ERA taking too much cpu on our live SQL Server. Is there a proper way to investigate this? or any right solution we can do something about it? Our ESET ERA and its database (SQL Server) are on the same server.