Microsoft Knowledge Base Email Alertz

The 'affinity mask' and 'affinity I/O mask' configuration should not conflict

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 2157114 - Last Review: April 2, 2012 - Revision: 2.0

The 'affinity mask' and 'affinity I/O mask' configuration should not conflict

SUMMARY

The 'affinity mask' and 'affinity I/O mask' configuration values of SQL Server should not conflict. Performance may suffer if you choose to affinitize a processor for both SQL Server worker thread scheduling and for I/O processing. Therefore, you should ensure that the configuration values are not set for the same processor. The same recommendation applies to the 'affinity64 mask' and 'affinity64 I/O mask'.

MORE INFORMATION

If these configuration values do conflict, when you try to run the RECONFIGURE command, the following error will occur:

Msg 5834, Level 16, State 1, Line 1
The affinity mask specified conflicts with the IO affinity mask specified. Use the override option to force this configuration

You would have to execute RECONFIGURE WITH OVERRIDE to allow these settings to be used for the next restart.

For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:

Collapse this tableExpand this table
Rule softwareRule titleRule descriptionProduct versions against which the rule is evaluated
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)





Conflicting affinity mask settings detected






The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect a conflict with the 'affinity mask' and 'affinity I/O mask' configuration. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2.

If you run the BPA tool and encounter an Error with the title of Engine - Conflicting affinity mask settings detected, then your SQL Server 2008 or SQL Server 2008 R2 installation has a has a conflict with the 'affinity mask' and 'affinity I/O mask' values (and 'affinity64mask' and 'affinity64 I/O mask') as found in sys.configurations (the "value_in_use"). BPA uses SMO to find the run value of this configuration.
SQL Server 2008
SQL Server 2008 R2







SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)





Conflicting affinity mask settings detected





The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect a conflict with the 'affinity mask' and 'affinity I/O mask' configuration.

If you run the BPA tool and encounter an Error with the title of Engine - Conflicting affinity mask settings detected, then your SQL Server 2008 or SQL Server 2008 R2 installation has a has a conflict with the 'affinity mask' and 'affinity I/O mask' values (and 'affinity64mask' and 'affinity64 I/O mask') as found in sys.configurations (the "value_in_use"). BPA uses SMO to find the run value of this configuration.
SQL Server 2012









APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
Keywords: 
KB2157114
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate