Leave new Gary. Kendra Little. Lincoln Bovee. A very useful post. We are running Sophos and were unaware of Sophos issue. Thanks Kendra! Derek Schoeters. Chad Miller. Anthony Douglas. Gene Torres. Kenneth Martin. Brent Ozar.
Ian Spencer. Peter Nauta. Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search.
Some implementations of antivirus software are known to Microsoft to cause a variety of problems for SQL Server , and Microsoft has a support article dedicated just to picking the right antivirus software for your SQL Server hosts. For me, personally, I have not found it practical. Extremely limited access, no browsing from the server, no hosting of file shares, rigorous firewall protection, principle of least privilege, etc. In my experience anti-virus is often a false security blanket.
It is either responding as a post-mortem correction or, in some cases, doesn't have the signature yet for the new threat - either because it is not kept up to date by the system administrator or by the vendor or both. Since rules and exceptions can change over time, if sysadmins can't keep anti-virus signatures up to date, how will they keep the rules and exceptions up to date?
Your goal should be to secure SQL Server so that you aren't concerned about anti-virus. If you're not having sex, you don't need to buy condoms. Yes, as long as you are excluding folders where SQL Server Data, Log and backup files are kept fron antivirus scanning.
Make sure you also exclude certain known file extensions like. Microsoft Support KB provide in-depth information related to consideration for running antivirus software on SQL Server machines. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? The purpose of this document is to provide a list of recommended antivirus exclusions for SQL Server in order to maintain Enterprise Vault, Compliance Accelerator and Discovery Accelerator data integrity.
Configuring the following antivirus exclusions verifies any files required by SQL are not locked or modified by antivirus software when they are needed. Overall SQL Server performance may also be improved by implementing the following antivirus exclusions, especially when using Discovery Accelerator Analytics.
These guidelines apply to both Real-Time and On-Demand antivirus scanning. It is important to reach a balance between a secure server antivirus configuration that does not cause reliability issues and performance degradation; therefore, it is highly recommended that any SQL Server antivirus exclusions be tested in a test environment while subjected to the maximum load expected in a production environment.
Important: The locations listed below are based on a default installation of SQL. If the SQL installation paths have been customized, be sure to adjust the antivirus exclusion locations accordingly.
These locations contain the Analysis data files, Analytics temporary files, Analysis Log files and Analysis backup files. These files usually have the following extensions:. Extended Events files These files contain any Extended Events Trace log files and can be contained in any folder as specified by a user when running an Extended Events Trace. DA version 8.
The following files must be excluded from antivirus scanning: - Configuration Database and Transaction Log files: These can be determined by reviewing the AcceleratorManager.
0コメント