Rename Server Process ID to Session ID

Author: rwestMSFT

azure-sql/database/understand-resolve-blocking.md

@@ -41,7 +41,7 @@ For connection operations, the Microsoft SqlClient Data Provider for SQL Server
 You can get the client connection ID programmatically by using the `SqlConnection.ClientConnectionID` property.
 
 > [!NOTE]
-> The Microsoft SqlClient Data Provider for SQL Server supports the server process ID since version 2.1.0. You can get it programmatically by using the `SqlConnection.ServerProcessId` property.
+> The Microsoft SqlClient Data Provider for SQL Server supports the session ID (SPID) since version 2.1.0. You can get it programmatically by using the `SqlConnection.ServerProcessId` property.
 
 The `ClientConnectionID` and `ServerProcessId` are available for a <xref:Microsoft.Data.SqlClient.SqlConnection> object that successfully establishes a connection. If a connection attempt fails, `ClientConnectionID` may be available via `SqlException.ToString`.
 

docs/connect/ado-net/data-tracing.md

@@ -914,14 +914,14 @@ public enum SensitivityRank
 }
 ```
 
-### Server Process ID for an active `SqlConnection`
+### Session ID for an active `SqlConnection`
 
 Microsoft.Data.SqlClient v2.1 introduces a new `SqlConnection` property, `ServerProcessId`, on an active connection.
 
 ```csharp
 public class SqlConnection
 {
-    // Returns the server process Id (SPID) of the active connection.
+    // Returns the session ID (SPID) of the active connection.
     public int ServerProcessId;
 }
 ```

docs/connect/ado-net/introduction-microsoft-data-sqlclient-namespace.md

@@ -157,7 +157,7 @@ Java.exe -Djava.security.auth.login.config=SQLJDBCDriver.conf -Djava.security.kr
 Run the following query in SQL Server Management Studio:
 
 ```sql
-select auth_scheme from sys.dm_exec_connections where session_id=\@\@spid
+select auth_scheme from sys.dm_exec_connections where session_id=@@spid
 ```
 
 Make sure that you have the necessary permission to run this query.

docs/connect/jdbc/using-kerberos-integrated-authentication-to-connect-to-sql-server.md

@@ -389,7 +389,7 @@ Allows long type data to be sent to servers as max type data.
 
 ### SQL_COPT_SS_SPID
 
-Retrieves the server process ID of the connection. This property is equivalent to the T-SQL [@@SPID](../../t-sql/functions/spid-transact-sql.md) variable, except that it doesn't incur an extra round trip to the server.
+Retrieves the session ID of the connection. This property is equivalent to the T-SQL [@@SPID](../../t-sql/functions/spid-transact-sql.md) variable, except that it doesn't incur an extra round trip to the server.
 
 | Attribute Value | Description |
 |-|-|

docs/connect/odbc/dsn-connection-string-attribute.md

@@ -36,7 +36,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 |**RoleName**|**nvarchar**|The role of the conversation handle. This is either **initiator** or **target**.|38|No|  
 |**ServerName**|**nvarchar**|The name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] being traced.|26|No|  
 |**Severity**|**int**|The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error severity, if this event reports an error.|29|No|  
-|**SPID**|**int**|The server process ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
+|**SPID**|**int**|The session ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
 |**StartTime**|**datetime**|The time at which the event started, when available.|14|Yes|  
 |**State**|**int**|Indicates the location within the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] source code that produced the event. Each location that may produce this event has a different state code. A Microsoft support engineer can use this state code to find where the event was produced.|30|No|  
 |**TextData**|**ntext**|For errors, contains a message that describes the reason for the failure. One of the following values:<br /><br /> <br /><br /> **Cert not found**. The user specified for dialog protocol security has no certificate.<br /><br /> **Not in valid time period**. The user specified for dialog protocol security has a certificate, but the certificate has expired.<br /><br /> **Cert too large for memory allocation**. The user specified for dialog protocol security has a certificate, but the certificate is too large. The maximum certificate size that Service Broker supports is 32,768 bytes.<br /><br /> **Private key not found**. The user specified for dialog protocol security has a certificate, but there is no private key associated with that certificate.<br /><br /> **The cert's private key size is incompatible with the crypto provider**. The private key for the certificate has a key size that cannot be successfully processed. The private key size must be a multiple of 64 bytes.<br /><br /> **The cert's public key size is incompatible with the crypto provider**. The public key for the certificate has a key size that cannot be successfully processed. The public key size must be a multiple of 64 bytes.<br /><br /> **The cert's private key size is incompatible with the encrypted key exchange key**. The key size specified in the key exchange key does not match the size of the private key for the certificate. This generally indicates that the certificate on the remote computer does not match the certificate in the database.<br /><br /> **The cert's public key size is incompatible with the security header's signature**. The security header contains a signature that cannot be validated with the certificate's public key. This generally indicates that the certificate on the remote computer does not match the certificate in the database.|1|Yes|  

docs/relational-databases/event-classes/audit-broker-conversation-event-class.md

@@ -36,7 +36,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 |**ProviderName**|**nvarchar**|The authentication method used for this connection|46|No|  
 |**RoleName**|**nvarchar**|The role of the connection. This is either **initiator** or **target**.|38|No|  
 |**ServerName**|**nvarchar**|The name of the instance of SQL Server being traced.|26|No|  
-|**SPID**|**int**|The server process ID assigned by SQL Server to the process associated with the client.|12|Yes|  
+|**SPID**|**int**|The session ID assigned by SQL Server to the process associated with the client.|12|Yes|  
 |**StartTime**|**datetime**|The time at which the event started, when available.|14|Yes|  
 |**State**|**int**|Indicates the location within the SQL Server source code that produced the event. Each location that may produce this event has a different state code. A Microsoft support engineer can use this state code to find where the event was produced.|30|No|  
 |**TargetUserName**|**nvarchar**|Login state. One of:<br /><br /> INITIAL<br /><br /> WAIT LOGIN NEGOTIATE<br /><br /> ONE ISC<br /><br /> ONE ASC<br /><br /> TWO ISC<br /><br /> TWO ASC<br /><br /> WAIT ISC Confirm<br /><br /> WAIT ASC Confirm<br /><br /> WAIT REJECT<br /><br /> WAIT PRE-MASTER SECRET<br /><br /> WAIT VALIDATION<br /><br /> WAIT ARBITRATION<br /><br /> ONLINE<br /><br /> ERROR<br /><br /> <br /><br /> **Note**: ISC = Initiate Security Context. ASC = Accept Security Context|39|No|  

docs/relational-databases/event-classes/audit-broker-login-event-class.md

@@ -38,7 +38,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 |**ProviderName**|**nvarchar**|The authentication method used for this connection.|46|No|  
 |**RoleName**|**nvarchar**|The role of the connection. This is either **initiator** or **target**.|38|No|  
 |**ServerName**|**nvarchar**|The name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] being traced.|26|No|  
-|**SPID**|**int**|The server process ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
+|**SPID**|**int**|The session ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
 |**StartTime**|**datetime**|The time at which the event started, when available.|14|Yes|  
 |**State**|**int**|Indicates the location within the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] source code that produced the event. Each location that may produce this event has a different state code. A Microsoft support engineer can use this state code to find where the event was produced.|30|No|  
 |**TargetUserName**|**nvarchar**|Login state. One of:<br /><br /> **INITIAL**<br /><br /> **WAIT LOGIN NEGOTIATE**<br /><br /> **ONE ISC**<br /><br /> **ONE ASC**<br /><br /> **TWO ISC**<br /><br /> **TWO ASC**<br /><br /> **WAIT ISC Confirm**<br /><br /> **WAIT ASC Confirm**<br /><br /> **WAIT REJECT**<br /><br /> **WAIT PRE-MASTER SECRET**<br /><br /> **WAIT VALIDATION**<br /><br /> **WAIT ARBITRATION**<br /><br /> **ONLINE**<br /><br /> **ERROR**<br /><br /> <br /><br /> Note: ISC = Initiate Security Context. ASC = Accept Security Context.|39|No|  

docs/relational-databases/event-classes/audit-database-mirroring-login-event-class.md

@@ -34,7 +34,7 @@ monikerRange: ">=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-curren
 |**NTUserName**|**nvarchar**|The name of the user that owns the connection that generated this event.|6|Yes|  
 |**ObjectID**|**int**|The queue associated with this event.|22|No|  
 |**ServerName**|**nvarchar**|The name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] being traced.|26|No|  
-|**SPID**|**int**|The server process ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
+|**SPID**|**int**|The session ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
 |**StartTime**|**datetime**|The time at which the event started, when available.|14|Yes|  
 |**TransactionID**|**bigint**|The system-assigned ID of the transaction.|4|No|  
 |   |   |   |   |   |

docs/relational-databases/event-classes/broker-activation-event-class.md

@@ -37,7 +37,7 @@ monikerRange: ">=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-curren
 |**NTUserName**|**nvarchar**|The name of the user that owns the connection that generated this event.|6|Yes|  
 |**ObjectName**|**nvarchar**|The conversation handle of the dialog.|34|No|  
 |**ServerName**|**nvarchar**|The name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] being traced.|26|No|  
-|**SPID**|**int**|The server process ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
+|**SPID**|**int**|The session ID assigned by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to the process associated with the client.|12|Yes|  
 |**StartTime**|**datetime**|The time at which the event started, when available.|14|Yes|  
 |**TextData**|**ntext**|The text of the error message related to the event. For events that do not report an error, this field is empty. The error message may either be a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error message or a Windows error message.|1|Yes|  
 |**TransactionID**|**bigint**|The system-assigned ID of the transaction.|4|No|