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 a row FOR EACH SOAP method defined on a SOAP-enabled HTTP endpoint. The combination of the endpoint_id and namespace columns is unique.
|Applies to: SQL Server ( SQL Server 2008 through current version).|
|Column name||Data type||Description|
|endpoint_id||int||ID of the endpoint that the webmethod is defined on.|
|namespace||nvarchar(384)||Namespace for the webmethod.|
|method_alias||nvarchar(64)||Alias for the method.
Note: Transact-SQL identifiers allow characters that are not legal in WSDL method names.
The alias is used to map the name exposed in the WSDL description of the endpoint to the actual underlying Transact-SQL executable object that is called when the webmethod is invoked.
|object_name||nvarchar(776)||The object name that the webmethod is redirected to, as specified in the NAME = option. Name parts are separated by a period (.), and delimited using brackets,
The object name must be a three-part name, as specified in the WSDL option.
|result_schema||tinyint||Option that determines which, if any, XSD is sent back with a response.
0 = None
1 = Standard
2 = Default
|result_schema_desc||nvarchar(60)||Description of option that determines which, if any, XSD is sent back with a response.
|result_format||tinyint||Option that determines how results are formatted in the response.
1 = ALL_RESULTS
2 = ROWSETS_ONLY
3 = NONE
|result_format_desc||nvarchar(60)||Description of the option that determines how results are formatted in the response.
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.