8/29/2008 0.5.1 Editorial Changed language and formatting in the technical content. 10/24/2008 0.5.2 Editorial Changed language and formatting in the technical content. 12/5/2008 0.6 Minor Clarified the meaning of the technical content. 1/16/2009 0.6.1 Editorial Changed language and formatting in the technical content. 2/27/2009 1.0 Major Updated and revised the technical content. 4/10/2009 1.0.1 Editorial Changed language and formatting in the technical content. 5/22/2009 1.1 Minor Clarified the meaning of the technical content. 7/2/2009 1.1.1 Editorial Changed language and formatting in the technical content. 8/14/2009 1.1.2 Editorial Changed language and formatting
in the technical content. 9/25/2009 1.2 Minor Clarified the meaning of the technical content. 11/6/2009 1.3 Minor Clarified the meaning of the technical content. 12/18/2009 1.3.1 Editorial Changed language and formatting in the technical content. 1/29/2010 1.4 Minor Clarified the meaning of the technical content. 3/12/2010 1.4.1 Editorial Changed language and formatting in the technical content. 4/23/2010 1.5 Minor Clarified the meaning of the technical content. 6/4/2010 1.6 Minor Clarified the meaning of the technical content. 7/16/2010 1.6 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 1.6 None No changes to the
meaning, language, or formatting of the technical content. 10/8/2010 2.0 Major Updated and revised the technical content. 11/19/2010 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 3.0 Major Updated and revised the technical content. 2/11/2011 4.0 Updated and revised the technical content. 3/25/2011 5.0 Updated and revised the technical content. 5/6/2011 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 5.1 Minor Clarified the meaning of the technical content. 9/23/2011 5.2 Minor Clarified the meaning of the
technical content. 12/16/2011 6.0 Updated and revised the technical content. 3/30/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 7.0 Major Updated and revised the technical content. 10/25/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 9.0 Major Updated and revised the technical content. 5/15/2014 9.0 None No changes to the meaning, language, or
formatting of the technical content. 6/30/2015 10.0 Major Significantly changed the technical content. 10/16/2015 10.0 None No changes to the meaning, language, or formatting of the technical content. 5/10/2016 11.0 Major Significantly changed the technical content. 7/14/2016 11.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 11.0 None No changes to the meaning, language, or formatting of the technical content. 8/16/2017 12.0 Significantly changed the technical content. 9/15/2017 13.0 Major Significantly changed the technical content. 9/12/2018 14.0 Major Significantly changed the
Messages Transport The SQL Server Resolution Protocol uses port 1434 of the UDP Protocol for message transport. When using the UDP Protocol over the Protocol, the SQL Server Resolution Protocol uses a or broadcast address, depending on the message type, as specified in section . When using the UDP Protocol over the Protocol, the SQL Server Resolution Protocol uses a unicast or address, depending on the message type, as specified in section 2.2. Message Syntax All integer fields are represented in format. All text strings are represented as a multibyte character set (MBCS) string on the current system code page of the server and the client. (The system code page on the client and the system code page on the server are assumed to be common.) They are not case-sensitive. See for more information. The valid requests from the client are as follows: The response from the server is always an message. The response contains a string data field that is parsed by the client to extract the requested information. The contents of this string are not These messages are explained in more detail in the following sections. CLNT_BCAST_EX The CLNT_BCAST_EX packet is a or request that is generated by clients that are trying to identify the list of database instances on the network and their network protocol connection information. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 CLNT_BCAST_EX CLNT_BCAST_EX (1 byte): A single byte value MUST be 0x02. CLNT_UCAST_EX The CLNT_UCAST_EX packet is a request that is generated by clients that are trying to identify the list of database instances and their network protocol connection information installed on a single machine. The client generates a UDP packet with a single byte, as shown in the following diagram. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 CLNT_UCAST_EX
A Abstract data model 18 16 9 C 9 26 Client 18 19 18 19 20 17 19 20 18 11 22 12 21 11 21 12 D Data model - abstract 18 16 E 21 F 10 G 6 H triggered events 19 16 I 23 23 7 Initialization 18 16 6 M Message processing 19 16 Messages 11 12 11 12 13 15 11 11 N 7 O Other local events 20 17 7 P 23 9 9 24 Protocol Details 16 R 7 7 7 9 S Security 23 23 Sequencing rules 19 16 Server 16 16 16 16 17 16 16 17