> I agree the software should be on the server, just not sure the
> configuration. There used to be a published configuration document on it from
> Microsoft.
>
> "Hank Arnold (MVP)" wrote:
>

>> Platypus wrote:

>>> This might not be "PC" but generally would not be recommending installing
>>> anti-virus software on a SQL Server box. And certainly there is no need for
>>> Diskeeper.
>>>
>>> Of course this depends on the business requirements, risk assessment and
>>> operational context, but there is no substitute for a properly "hardened",
>>> "configured" and "managed" SQL Server.
>>>
>>> I would suggest that defragmentation vendors tend to oversell the benefits
>>> (if any) of their software. Similarly to how screen-saver vendors sold their
>>> wares as a means of preventing "burn-in" of screens...
>>>
>>> Some thoughts anyway...
>>>
>>>
>>> "John Barr" wrote:
>>>

>>>> Does anyone know what the best configuration options are when running in a
>>>> server supporting SQL Server 2000/2005?
>>>>
>>>> I used to have documentation for this, but have since lost it.

>> I disagree somewhat on the AV comment. While "real time" scanning should
>> be disabled, the best practice (IMNSHO) is to have a regular scan done
>> over night. This scan should exclude certain files and folders, but
>> otherwise should be done. MS has excellent documentation on what to
>> exclude from AV scans....
>>
>> --
>>
>> Regards,
>> Hank Arnold
>> Microsoft MVP
>> Windows Server - Directory Services
>>