Most programs advise not to scan their executables -its a performance killer.
On most desktop systems, the interactions between the anti-virus software and client software is fairly localized. When anti-virus software is installed on a centralized corporate server such as a database machine, the effects of a misconfigured anti-virus package can be globally felt .
By design, databases and their associated control files are under constant and heavy use, meaning that any interference with these files could create issues (read corruption) within the database environment. Now introduce an anti-virus solution that has not been configured to take into account the application of the machine it is being installed on. It is conceivable that everything may run smoothly for a period of time before there are signs of trouble.
For example, passive anti-virus software scans that target any active database files may not pickup any suspicious looking data signatures and then a single small entry into the database could alter the data signature enough to look like a virus, causing the data files in question to be quarantined. Not a good scenario for an active system. The end result is usually the database goes offline, or worse, corrupts the control files needed to keep the system synchronized properly.
Active scanning can cause even more subtle issues both with performance of the database engine and corruption. When anti-virus software is actively scanning transaction files, there is an overhead introduced when the scan takes control of the file in question. Then depending on the action being performed against the database, it is possible that critical data can be lost if the active scan has locked a needed file for examination. Effects of this can be structure synchronization issues, data loss or data corruption. Recovery of these issues, if at all possible, can be costly and very time consuming.
Anti-virus packages can also consume significant operating system resources that may impact database performance
You can of course always schedule to scan out of hours- not ideal but its an option.
You might usefully check back to this post and the referenced white paper https://community.dynamics.com/ax/f/33/t/89749
Note you also need to consider ant- virus impacts on other components of your infrastructure.
Some other older references I still have:
Dynamics AX:
http://blogs.msdn.com/b/czdaxsup/archive/2010/05/13/ax-application-files-locked-by-another-process.aspx
Some sources for this list include:
Virus scanning recommendations for Enterprise computers that are running currently supported versions of Windows
http://support.microsoft.com/kb/822158
Anti-Virus Exclusions and You! – Dude where’s my PFE? – Site Home – TechNet Blogs
http://blogs.technet.com/b/jeff_stokes/archive/2010/05/19/anti-virus-exclusions-and-you.aspx
Windows Anti Virus Exclusion List – TechNet Articles – Home – TechNet Wiki
http://social.technet.microsoft.com/wiki/contents/articles/953.aspx
https://blogs.technet.microsoft.com/raymond_ris/2014/01/16/windows-antivirus-exclusion-recommendations-servers-clients-and-role-specific/
https://support.isheriff.com/support/solutions/articles/197183-recommended-anti-virus-exclusions-list
https://kc.mcafee.com/corporate/index?page=content&id=KB57308
