Updated: June 10, 2016
Contains a row for each conversation priority created in the current database, as shown in the following table:
|Column name||Data type||Description|
|Priority_id||int||A number that uniquely identifies the conversation priority. Not NULLABLE.|
|name||sysname||Name of the conversation priority. Not NULLABLE.|
|service_contract_id||int||The identifier of the contract that is specified for the conversation priority. This can be joined on the service_contract_id column in sys.service_contracts. NULLABLE.|
|local_service_id||int||The identifier of the service that is specified as the local service for the conversation priority. This column can be joined on the service_id column in sys.services. NULLABLE.|
|remote_service_name||nvarchar(256)||The name of the service that is specified as the remote service for the conversation priority. NULLABLE.|
|priority||tinyint||The priority level that is specified in this conversation priority. Not NULLABLE.|
The visibility of the metadata in catalog views is limited to securables that a user either owns or on which the user has been granted some permission. For more information, see Metadata Visibility Configuration.
The following example lists the conversation priorities by using joins to show the contract and local service names.
SELECT scp.name AS priority_name, ssc.name AS contract_name, ssvc.name AS local_service_name, scp.remote_service_name, scp.priority AS priority_level FROM sys.conversation_priorities AS scp INNER JOIN sys.service_contracts AS ssc ON scp.service_contract_id = ssc.service_contract_id INNER JOIN sys.services AS ssvc ON scp.local_service_id = ssvc.service_id ORDER BY priority_name, contract_name, local_service_name, remote_service_name;