Can anyone tell me what I can do to make Symantec work good with SQL box. what needs to be blocked or enabled in SQL so my database will not get corrupted. This is a new SQL windows 2008 standard box.
I just installed Symantec 11.0 V on it and it was not installing due to ACL account permission. I had to disbale the account first and than I was able to install the symantec anti virus on the sql box.
now all I need is someone too tell me exactly what I need to disable or enable on the SQL box so my data box does not get corrupted at all. Is there anything in Symantec Anti virus that I need to disable or on SQl please give me details.
I found this on the internet. :
Now, there are a few configuration changes (in my opinion) that should be made since it is a SQL Server.
Don’t try and scan the mdf, ndf, or ldf files. SQL Server has them locked so the anti-virus will just error out when it tries to scan them anyway. And if the SQL Server is stopped and the anti-virus thinks that it sees a virus in the files, it’ll just corrupt the file when it tries to clean it.
Make sure that your scans are being done at a time which is appropriate for the load on the SQL Server at that time. If the scan runs during the day and its an OLTP system, probably not the best idea. If its an OLAP database then the middle of the night, when the load is running or the early morning when reports are running probably isn’t the best time.
Tell the anti-virus not to do real time scanning of your backup folder (weekly scanning is fine), but this will slow down your backup and restore time. Make sure that all it does is tell someone if the backup file has a virus, we don’t want it to corrupt the SQL Backup by accident either.
Have other rules that you follow? Or a conflicting idea?