﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Brian Kelley / Article Discussions / Article Discussions by Author  / SQL Server Security: Dealing with Anti-Virus Programs / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 25 May 2013 08:27:51 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQL Server Security: Dealing with Anti-Virus Programs</title><link>http://www.sqlservercentral.com/Forums/Topic115032-59-1.aspx</link><description>&lt;P&gt;Your article was very clear and concise.  I have Symantec AV client running on my SQL Servers, and the reason I excluded the database files was the possibility that the AV software might quarantine one of them!  I had that problem initially with Exchange log files on another server until I sorted it out.&lt;/P&gt;&lt;P&gt;Thanks for the article.&lt;/P&gt;</description><pubDate>Thu, 13 May 2004 08:47:00 GMT</pubDate><dc:creator>jbheather</dc:creator></item><item><title>RE: SQL Server Security: Dealing with Anti-Virus Programs</title><link>http://www.sqlservercentral.com/Forums/Topic115032-59-1.aspx</link><description>&lt;P&gt;An excellent article that meets its stated goal.  The explanations are well stated and allow for other points of view and discussion.&lt;/P&gt;&lt;P&gt;I especially appreciate the pointers to the knowledge base articles, and other web sites. that allow me to further research and convince others of the risks and benefits.  In other articles, especially other web sites, these links are often times missing, which may leave unanswered questions.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description><pubDate>Thu, 13 May 2004 07:34:00 GMT</pubDate><dc:creator>Peter Kryszak</dc:creator></item><item><title>RE: SQL Server Security: Dealing with Anti-Virus Programs</title><link>http://www.sqlservercentral.com/Forums/Topic115032-59-1.aspx</link><description>&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;Good article Brian!&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;One thing I would like to add.  Backing up SQL Server databases using a perl script (or any other type of OS scripting language script) is a very good idea.  It allows you to very easily enforce backup and restore standards and methodologies.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;Although you could conceivably perform all the operations you need to do using T-SQL and xp_cmdshell, I find Perl gives greater flexibility and ease of maintenance.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;If you are performing your backups uniformly using an OS shell script, it is very easy to configure security and virus scanning for the file system for all of the SQL Servers you may be managing.&lt;/SPAN&gt;&lt;/P&gt;</description><pubDate>Thu, 13 May 2004 07:29:00 GMT</pubDate><dc:creator>Jeremy Brown</dc:creator></item><item><title>SQL Server Security: Dealing with Anti-Virus Programs</title><link>http://www.sqlservercentral.com/Forums/Topic115032-59-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/bkelley/sqlserversecuritydealingwithantivirusprograms.asp&gt;http://www.sqlservercentral.c</description><pubDate>Fri, 07 May 2004 17:08:00 GMT</pubDate><dc:creator>K. Brian Kelley</dc:creator></item></channel></rss>