anti-virus on sql server box?

hi!

i am using sql 2005 with sp1 standard edition.

i have a question regarding the antivirus software. Is it ok to install anti-virus software on the sql server box? what are the issues involved if we install anti-virus software on the sql server box?
I heard, it causes some performance and other issues.

Is there anything we need to take care of .if we decide to install anti-virus software on the sql server box?

Can anybody share experience on this?

Thanks

Personally, I am very much against installing anti-virus software on a SQL Server box, for performance reasons. You see conflicting advice from Microsoft about this. The Perf people say no, and the security people say yes. If you decide to run AV on your SQL Server, make sure to exclude the data and log files from the scanning.|||

Generally speaking, it is not a good idea to have anti-virus products on a SQL Server.

Consider that anti-virus products protect the computer from user activities in the Workstation service.

On a SQL Server, there 'should' not be any user activities in the Workstation service.

|||I disagree with the other posts here.

ALWAYS run anti-virus on ALL machines on the network, servers and pcs, with current virus defs.

On SQL server, exclude the data and log directories from the scanning and virus protection.

Many viruses will infect all machines on the entire network, and if you don't have AV on ALL machines, when you remove it from all your PCs, it will hide on your SQL server box until it infects the entire network again and again and again. I know because this has happened to me, with more than one customer who has the same "performance" concerns.
|||Yes, I agree with Tlom. There are several approaches, defined by the policy of the companies which way you can take if you secure SQL Server. You can either exclude the data file and directories or exclude the appropuiate MDF / LDF extensions (which assumes that you are using these extensions with your files) I prefer the extensions exclusion which will makes it even not possible to inject a virus in the data directories of SQL Server.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Thank you everyone for your replies. I really appreciate it.

So if you exclude the data and log files, are there any performance issues and other issues like communication/blocking etc ?

Thanks
|||

I hope this will help you:

Guidelines for choosing antivirus software to run on the computers that are running SQL Server

http://support.microsoft.com/kb/309422/en-us

Anti-Virus on SQL Configuration

Hi:
We have Symantec Enterprise Anti-Virus 10.0 but it is not currently
installed on our new SQL box. I would like to know what files and folders t
o
exclude from scanning before I install. I have search Symantec knowledgebas
e
but no answers. Does MS have a page on this like they do for Exchange or is
it pretty much the same as Exchange?
Thanks,http://support.microsoft.com/?kbid=309422
http://www.sqlservercentral.com/col...rusprograms.asp
Andrew J. Kelly SQL MVP
"Cindy" <Cindy@.discussions.microsoft.com> wrote in message
news:1C577C85-E5D4-48B0-BBE1-B363C06C706B@.microsoft.com...
> Hi:
> We have Symantec Enterprise Anti-Virus 10.0 but it is not currently
> installed on our new SQL box. I would like to know what files and folders
> to
> exclude from scanning before I install. I have search Symantec
> knowledgebase
> but no answers. Does MS have a page on this like they do for Exchange or
> is
> it pretty much the same as Exchange?
> Thanks,|||Thanks Andrew. It would be nice if MS had step by step like with Exchange.
Symantec has nothing but the other article you pointed me to helps.
Cindy
"Andrew J. Kelly" wrote:

> http://support.microsoft.com/?kbid=309422
>
> http://www.sqlservercentral.com/col...rusprograms.asp
>
>
> --
> Andrew J. Kelly SQL MVP
>
> "Cindy" <Cindy@.discussions.microsoft.com> wrote in message
> news:1C577C85-E5D4-48B0-BBE1-B363C06C706B@.microsoft.com...
>
>

ANSI defaults, Linked Server

Hey all,
I have a linked server on our SQL 2000 box, which points to PCCW.mdb; An
Access database that our Credit Card processing software uses. I have
written a SP to grab some data from this Linked Server, and from my local SQ
L
database. The Syntax check on the SP goes fine, but when I try to save the
SP, I get the warning:
"Error 7405: Heterogeneous queries require the ANSI_NULLS and ANSI_Warnings
options to be set for the connection. This ensures consistent query
semantics. Enable these options and the reissue your query"
In the SP I am issuing the commands for ANSI_NULLS and ANSI_WARNINGS (will
post below), and when I run the SELECT statement contained in the SP through
Query Analyzer, it works fine. Any help is always appreciated, and thanks i
n
advance.
Gerard - SP posted below
CREATE PROCEDURE spBasSunLyncInBadCredit
AS
SET ANSI_NULLS ON
SET ANSI_WARNINGS ON
SELECT tblCreditCardControl.CID, PCCW..Trans.[Date], PCCW..Trans.[Time],
PCCW..Trans.Card, PCCW..Trans.TID, PCCW..Trans.Issuer, PCCW..Trans.Member,
PCCW..Trans.ExpDate, PCCW..Trans.Amount, PCCW..Trans.Status,
PCCW..Trans.Auth, PCCW..Trans.BatchNumber, PCCW..Trans.Ticket FROM
PCCW...Trans INNER JOIN tblCreditCardControl ON PCCW..Trans.TID =
tblCreditCardControl.MerchantNumber WHERE ((tblCreditCardControl.CID = '357'
)
AND (PCCW..Trans.Status = 'C') AND (PCCW..Trans.[Date] = '2/7/05'))
GOWhere are you creating the sp in EM?, Try using QA.
BUG: Can't Use SQL Enterprise Manager to Create Stored Procedures Containing
Linked Server Objects
http://support.microsoft.com/defaul...kb;en-us;296769
AMB
"Gerard" wrote:

> Hey all,
> I have a linked server on our SQL 2000 box, which points to PCCW.mdb;
An
> Access database that our Credit Card processing software uses. I have
> written a SP to grab some data from this Linked Server, and from my local
SQL
> database. The Syntax check on the SP goes fine, but when I try to save th
e
> SP, I get the warning:
> "Error 7405: Heterogeneous queries require the ANSI_NULLS and ANSI_Warning
s
> options to be set for the connection. This ensures consistent query
> semantics. Enable these options and the reissue your query"
> In the SP I am issuing the commands for ANSI_NULLS and ANSI_WARNINGS (will
> post below), and when I run the SELECT statement contained in the SP throu
gh
> Query Analyzer, it works fine. Any help is always appreciated, and thanks
in
> advance.
> Gerard - SP posted below
> CREATE PROCEDURE spBasSunLyncInBadCredit
> AS
> SET ANSI_NULLS ON
> SET ANSI_WARNINGS ON
> SELECT tblCreditCardControl.CID, PCCW..Trans.[Date], PCCW..Trans.[Time],
> PCCW..Trans.Card, PCCW..Trans.TID, PCCW..Trans.Issuer, PCCW..Trans.Member,
> PCCW..Trans.ExpDate, PCCW..Trans.Amount, PCCW..Trans.Status,
> PCCW..Trans.Auth, PCCW..Trans.BatchNumber, PCCW..Trans.Ticket FROM
> PCCW...Trans INNER JOIN tblCreditCardControl ON PCCW..Trans.TID =
> tblCreditCardControl.MerchantNumber WHERE ((tblCreditCardControl.CID = '35
7')
> AND (PCCW..Trans.Status = 'C') AND (PCCW..Trans.[Date] = '2/7/05'))
> GO