Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am advising someone on how to disable TCP Chimney Offload, which is enabled by default by Windows Server 2003 SP2. We are working in an environment with multiple server machines, namely the application server machine which communicates with the database server machine.

This can cause communication problems between application and database. See KB942861 and Windows Scalable Networking Pack - Possible Performance and Concurrency Impacts to SQL Server Workloads.

On which machine should TCP Chimney Offload be disabled? Application, database or both?

share|improve this question
add comment

migrated from stackoverflow.com Jul 2 '13 at 14:32

This question came from our site for professional and enthusiast programmers.

1 Answer

up vote 8 down vote accepted

Bit of a carbon copy of a previous answer...

Personally, I disable it at both ends of the pipe but the problem usually manifests at the database end (due to the comparatively high traffic). As described in this MSDN blog post, I would start with disabling in the OS with:

netsh int ip set chimney DISABLED

It may be necessary to disable the features at the card driver level in some cases. It certainly won't hurt to do so by default.

share|improve this answer
    
thanks for the additional detail, it helps! –  d3vid Jul 2 '13 at 14:56
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.