So now we know this connection is from a client using SQL Server 2008 driver. Note the rest of the hex digits (0A0003) are intermediate build and minor version.ģ. you may have to copy and paste the link to your browser).
Take the first two hex digits (0x73) and map it to correct SQL Server version based on the table below ( Convert the above protocol_version to hex format.Ģ. The integer value is the representation of TDS version (for TSQL). Well, the big number still doesn’t say which version of data access driver, does it? Actually it does. Select protocol_type, protocol_version from sys.dm_exec_connections Basically it tells what protocol is associated with the client connection. Looking at sys.dm_exec_connections, there is a column protocol_version, which according to BOL means “Version of the data access protocol associated with this connection”.
#Education microsoft sql server client access licenses driver
For more info about the driver difference, check outĪfter struggling to find out from application server what version of SNAC actually was being used by the deployed application, we decided to probe from SQL Server side. It’s important to determine which version of SNAC was used as there are additional features in SNAC 10 that are not supported in SNAC 9 and cause different behavior of the application. And the application is designed to support both. In the mixed environment, some application server machines have SNAC 9 (shipped with SQL Server 2005) and SNAC 10 (shipped with SQL Server 2008) installed side by side. It comes down to finding out which version of SQL Server driver the application uses for connection. In a recent engagement with an ISV, we’ve run into a sporadic application failure problem when the application is deployed in a mixed environment.
0 kommentar(er)
