Re: NIC settings for SQL 2005 and windows 2003?

But you have been getting responses from SQL MVPs : )

-Sue

On Mon, 14 Aug 2006 12:13:49 -0400, "DBA Dude"
<code@xxxxxxxx> wrote:

The odd thing is the only thing you're all recommending are articles by
Microsoft. Not actual performance testing on your own. Thus, i tend to
believe the Microsoft SQL MVP's who have actually done performance testing
with both settings.


"Keith Kratochvil" <sqlguy.back2u@xxxxxxxxxxx> wrote in message
news:%23LZnGA7vGHA.4868@xxxxxxxxxxxxxxxxxxxxxxx
This Books Online article mentions that the SQL Server setup configures
the setting for network applications "enabling the server to accommodate
more connections. Although maximizing throughput for network applications
is recommended, you can change this setting."
http://msdn2.microsoft.com/en-us/library/ms191471.aspx

This article http://msdn2.microsoft.com/en-us/library/ms179301.aspx
mentions:
"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."

It also mentions [When setting up AWE] "The Maximize data throughput for
network application option of Network Connection in Control Panel must be
selected."


I remember reading an article (I can't find the link now) that mentioned
you should choose file sharing. I don't remember where I found the
article or the reasoning behind their suggestion, but I would be tempted
to go with the "network applications" selection.

--
Keith Kratochvil


"DBA Dude" <code@xxxxxxxx> wrote in message
news:OlCxvMMvGHA.4436@xxxxxxxxxxxxxxxxxxxxxxx
Hi Arnie

It would seem so, but this fellow Microsoft MVP in SQL, say's that isn't
true. That when you combine the SQL 2005 with windows 2003, you sould
always use the ""Maximize date throughput for file sharing" setting.

Anyone else have opinions?

Thanks



"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:u$ndEiJvGHA.1436@xxxxxxxxxxxxxxxxxxxxxxx
If the primary use of the server is SQL Server, then it is a 'network
application'
(If the primary use is file storage, then it is 'file sharing'.)

Typically, for an OLTP database you want smaller TCP packets, for an
OLAP database, larger TCP packets.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"DBA Dude" <code@xxxxxxxx> wrote in message
news:OsqdVVJvGHA.2436@xxxxxxxxxxxxxxxxxxxxxxx
All

Anyone know what is truly recommended for the NIC settings for SQL 2005
when installed on Windows 2003?

Microsoft SQL MVP and SQL author: Mark L. states that the NIC should be
set to:

"Maximize date throughput for file sharing."

However, MSDN article states that the setting should be:

"Maximize data throughput for network applications."

Anyone have any definitive resource on actually what it should be set
at?

Thank you

DBA DAB









.

Relevant Pages

  • Re: NIC settings for SQL 2005 and windows 2003?
    ... I appreciate your defense of technical writers, but they are just that, ... The people I know who write for Microsoft are actually very ... with SQL Server 2005: ... Maximize data throughput for network applications (the option that ...
    (microsoft.public.sqlserver.connect)
  • Re: Very strange behavior of SQLServer with connection from CGI
    ... this is not a default SQL instance. ... SQL clients use a UDP ... connection to port 1434 to resolve port numbers for named instances. ... You can use the SQL Server Network utility to lock ...
    (microsoft.public.sqlserver.connect)
  • Re: Very strange behavior of SQLServer with connection from CGI
    ... this is not a default SQL instance. ... SQL clients use a UDP ... connection to port 1434 to resolve port numbers for named instances. ... You can use the SQL Server Network utility to lock ...
    (microsoft.public.sqlserver.clustering)
  • Re: Very strange behavior of SQLServer with connection from CGI
    ... this is not a default SQL instance. ... SQL clients use a UDP ... connection to port 1434 to resolve port numbers for named instances. ... You can use the SQL Server Network utility to lock ...
    (microsoft.public.sqlserver.security)
  • Re: Connection from remote computer to network SQL Server
    ... by default connectin to SQL Express from the network is disabled ... There is no firewall on the W2K machine acting as the SQL server. ... connection works. ...
    (microsoft.public.access.adp.sqlserver)
Loading