This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
Contains one row for each endpoint in the server that carries a SOAP-type payload. For every row in this view, there is a corresponding row with the same endpoint_id in the sys.http_endpoints catalog view that carries the HTTP configuration metadata.
For a list of columns that this view inherits, see sys.endpoints (Transact-SQL).
1 = BATCHES = ENABLED option was specified, meaning that ad-hoc SQL batches are allowed on the endpoint.
The three-part name of the stored procedure that implements this method.
Names of methods require strict three-part syntax. one, two, or four-part names are not allowed.
The name of the default database given in the DATABASE = option.
NULL = DEFAULT was specified.
The default namespace specified in the NAMESPACE = option, or 'http://tempuri.org' if DEFAULT was specified instead.
The default value of the SCHEMA = option.
0 = NONE
1 = STANDARD
Description of the default value of the SCHEMA = option.
0 = CHARACTER_SET = SQL option was specified.
1 = CHARACTER_SET = XML option was specified.
0 = SESSION = DISABLE option was specified.
1 = SESSION = ENABLED option was specified.
Value specified in SESSION_TIMEOUT = option.
Kind of authentication allowed on this endpoint.
Maximum allowable size of the SOAP header.
In SQL Server 2005 and later versions, 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.