SQL 2000 - Network Packet Size Parameter

  • Question I can not seem to find answered. IF I have a client who is running GB copper ethernet to all servers and workstations should we mess with the Network Packet size? 🙂

  • The type of network use is a relatively minor factor in this equation.  The more important factors are the average size of the requests being sent to the server and the average size of the response. 

    Generally, the requests aren't very big either so the most important thing tends to be the size of the responses.  If your server tends to send large result sets in response to queries it might make sense to increase the packet size so that fewer packets have to be built.  If on the other hand all your query results are very small you should probably decrease the packet size so that there is less wasted space in each packet.

    4k is a pretty good balance for most instances.

    /*****************

    If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek

    *****************/

  • Totally agree with DC - getting a network guru to analyse your traffic 4k is good - but in heavy insert environments I have found 8k to be better as it is also SQL's page size.

  • Thanks guys, I am talking with our developer now and we are going to run some tests and see what we get then look at this issue further.

     

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply