6 Appendix A: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.
Microsoft SQL Server 2005
Microsoft SQL Server 2008
Microsoft SQL Server 2008 R2
Microsoft SQL Server 2012
Microsoft SQL Server 2014
Microsoft SQL Server 2016
Windows Vista operating system
Windows Server 2008 operating system
Windows 7 operating system
Windows Server 2008 R2 operating system
Windows 8 operating system
Windows Server 2012 operating system
Windows 8.1 operating system
Windows Server 2012 R2 operating system
Windows 10 operating system
Windows Server 2016 operating system
Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.
<1> Section 2.1: Microsoft SQL Server supports TCP and named pipes as transport protocols for the SMP protocol. In addition, SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 support the VIA protocol as a protocol configuration option that can be used as the underlying transport.
<2> Section 3.1: SQL Server supports TCP and named pipes as transport protocols for the SMP protocol. In addition, SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 support the VIA protocol as a protocol configuration option that can be used as the underlying transport.
<3> Section 18.104.22.168.3: In Microsoft implementations, when the SMP layer sends a packet, the value of the LastHighWaterForRecv ADM variable is set to the value of the WNDW field of the sent packet.
In Microsoft implementations, a delayed acknowledgement algorithm is implemented by sending an ACK packet after every other DATA packet that is retrieved by the higher layer. In the implementation example provided in section 22.214.171.124.3, an ACK packet is sent if the value of the HighWaterForRecv ADM variable minus the value of the LastHighWaterForRecv ADM variable is greater than or equal to 2.