Search the Community
Showing results for tags 'sql server'.
Hello, after successfully migrating to a new server, I can communicate properly with all the agents. But the PROTECT Server no longer sees any of the licenses used in it. (MSP\BA + Single Serial ones - over a 100) I can see all the licenses in SQL but not in the management console.
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://support.microsoft.com/en-us/help/4557397/cumulative-update-21-for-sql-server-2017
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 my ERA from v5 to v6) 2. Is there a proper way to move the era_db database from the ERASQL instance to the SQLEXPRESS instance? From this help link (https://help.eset.com/era_install/65/en-US/index.html?db_migration_sql.htm), if I understood correctly, this is not doable because the era_db cannot be moved to another instance that's lower version? If not doable, that means I would probably need to move all other databases from the SQLEXPRESS instance (v11.0.2100) to the newer instance (ERASQL, v12.0.2000) in order to let my server only need to run one instance? Thanks.
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.