Jump to content

Search the Community

Showing results for tags 'sql server'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • ESET General Forums
    • ESET Announcements
    • General Discussion
    • Forum FAQ's and Rules
    • Submit a virus, website or potential false positive sample to the ESET lab
    • Quick questions by guests (registration not required)
  • ESET Home User Products
    • ESET Internet Security & ESET Smart Security Premium
    • ESET NOD32 Antivirus
    • ESET Cyber Security (for Mac)
    • ESET Cyber Security Pro (for Mac)
    • ESET NOD32 Antivirus for Linux Desktop
    • ESET Products for Mobile Devices
    • Web portals
  • Malware Detection and Cleaning
    • Malware Finding and Cleaning
    • ESET Standalone Malware Removal Tools
  • ESET Business User Products
    • ESET Cloud solutions
    • ESET Endpoint Products
    • ESET Products for Windows Servers
    • ESET Products for Linux Servers
    • ESET Products for Mobile Devices
    • Remote Management
    • ESET Enterprise Inspector (EDR)
    • ESET Products for Virtualized Environments
    • Encryption
    • ESET Licensing for Business
    • Other ESET business products
  • ESET Beta Products
    • ESET Beta Products for Home Users
    • ESET Beta Products for Business Users
  • Slovak and Czech forums
    • ESET NOD32 Antivirus, ESET Internet Security a ESET Smart Security Premium
    • Produkty pre mobilné zariadenia
    • Vírusy a iné hrozby
    • Ostatné

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

AIM

MSN

Website URL

ICQ

Yahoo

Jabber

Skype

Interests

Found 3 results

  1. T3chGuy007
    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
  2. cmit
    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
  3. cmit
    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.
×
×
  • Create New...