Contradictory statement exists in BOL which is
version SQL 2005 SP1:
Local:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/29ce373e-18f8-46ff-aea6-
15bbb10fb9c2.htm
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/34950321-2bfd-4679-8f1b-
0a0a440eb443.htm
Online:
http://msdn2.microsoft.com/en-us/library/ms178067.aspx
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
Both documents address the setting "Maximize data throughput for network applications".
While both documents state "This option may limit memory available to SQL Server for normal operation". Then one document advises to enable and the other to
disable.
I would like to know if this is simply an oversight or if the contradiction is somehow correct and due to the context by which each document is presented.
I don't see where they contradict - they seem to say the same thing:
http://msdn2.microsoft.com/en-us/library/ms178067.aspx
"Maximize Data Throughput for Network Applications
If the Maximize data throughput for network applications network connection option is selected, the operating system gives priority to applications that perform buffered I/O operations by caching their I/O pages in file system cache. This option may limit memory available to SQL Server for normal operation."
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
"Maximize Data Throughput for Network Application
If the Maximize data throughput for file sharing option is selected in Network Connection, the operating system gives priority to applications that perform buffered input/output (I/O) operations by caching their I/O pages in file system cache. This option may limit memory available to SQL Server for normal operation."
Can you elaborate?
Thanks -
Buck Woody
|||But there is contradictory. You said in the first paragraf "If the Maximize data throughput for network applications network connection option is selected" and in the second paragraf you said "If the Maximize data throughput for file sharing option is selected "
What is the correct setting?
|||I see that now. It may be because one deals with SQL Server with no options, the other with AWE memory. When you enable AWE memory the large pool is a bit different. Sorry for the confusion.
No comments:
Post a Comment