April 12, 2013 at 12:00 am
AS per the explanation:
"You can create three payload types in SQL Server 2012: TCP, Service Broker, and Database Mirroring endpoints. SOAP endpoints were removed in SQL Server 2012."
When I refer to this link:
http://msdn.microsoft.com/en-in/library/ms162560.aspx
I found that SOAP is still in list of payload types.
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
April 12, 2013 at 2:03 am
Shouldn't TCP in the answers be TSQL?
TCP is one of the two protocols that can be used, TSQL is a payload type.
April 12, 2013 at 2:15 am
kapil_kk (4/12/2013)
AS per the explanation:"You can create three payload types in SQL Server 2012: TCP, Service Broker, and Database Mirroring endpoints. SOAP endpoints were removed in SQL Server 2012."
When I refer to this link:
http://msdn.microsoft.com/en-in/library/ms162560.aspx
I found that SOAP is still in list of payload types.
I agree I looked this up in BOL and found the same quote!!
Steve
April 12, 2013 at 3:49 am
sfayer (4/12/2013)
kapil_kk (4/12/2013)
AS per the explanation:"You can create three payload types in SQL Server 2012: TCP, Service Broker, and Database Mirroring endpoints. SOAP endpoints were removed in SQL Server 2012."
When I refer to this link:
http://msdn.microsoft.com/en-in/library/ms162560.aspx
I found that SOAP is still in list of payload types.
I agree I looked this up in BOL and found the same quote!!
Steve
+1
But, starting from SQL Server 2008: Native XML Web Services (SOAP/HTTP endpoints) is deprecated. For more information, see Native XML Web Services: Deprecated in SQL Server 2008.
So, in 2012 is removed!
April 12, 2013 at 5:00 am
Actually deprecated does not mean removed - it means currently supported but will be removed in future versions. So SOAP is a valid type.
April 12, 2013 at 5:50 am
PurpleLady (4/12/2013)
Actually deprecated does not mean removed - it means currently supported but will be removed in future versions. So SOAP is a valid type.
No, it is not. SOAP was deprecated in SQL Server 2008, and removed in SQL Server 2012. That may be unusual (normally deprecated features are kept around for a while), but it is true. The documentation Steve links to in the explanation is correct, the conflicting information found by Kapil_kk is incorrect.
Proof:
SELECT @@VERSION;
-- Code copied from SQL 2008 version of Books Online
CREATE ENDPOINT sql_endpoint
STATE = STARTED
AS HTTP(
PATH = '/sql',
AUTHENTICATION = (INTEGRATED ),
PORTS = ( CLEAR ),
SITE = 'SERVER'
)
FOR SOAP (
WEBMETHOD 'GetSqlInfo'
(name='master.dbo.xp_msver',
SCHEMA=STANDARD ),
WEBMETHOD 'DayAsNumber'
(name='master.sys.fn_MSdayasnumber'),
WSDL = DEFAULT,
SCHEMA = STANDARD,
DATABASE = 'master',
NAMESPACE = 'http://tempUri.org/'
);
GO
Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Msg 7878, Level 16, State 1, Line 2
This "CREATE ENDPOINT" statement is not supported on this edition of SQL Server.
April 12, 2013 at 5:59 am
From http://technet.microsoft.com/en-us/library/ms181591.aspx :
"The payload can be one of several supported types: Transact-SQL, service broker, database mirroring.
Note
Native XML Web Services (SOAP/HTTP endpoints) was removed in SQL Server 2012"
April 12, 2013 at 7:02 am
Hugo Kornelis (4/12/2013)
PurpleLady (4/12/2013)
Actually deprecated does not mean removed - it means currently supported but will be removed in future versions. So SOAP is a valid type.No, it is not. SOAP was deprecated in SQL Server 2008, and removed in SQL Server 2012. That may be unusual (normally deprecated features are kept around for a while), but it is true. The documentation Steve links to in the explanation is correct, the conflicting information found by Kapil_kk is incorrect.
Proof:
SELECT @@VERSION;-- Code copied from SQL 2008 version of Books Online
CREATE ENDPOINT sql_endpoint
STATE = STARTED
AS HTTP(
PATH = '/sql',
AUTHENTICATION = (INTEGRATED ),
PORTS = ( CLEAR ),
SITE = 'SERVER'
)
FOR SOAP (
WEBMETHOD 'GetSqlInfo'
(name='master.dbo.xp_msver',
SCHEMA=STANDARD ),
WEBMETHOD 'DayAsNumber'
(name='master.sys.fn_MSdayasnumber'),
WSDL = DEFAULT,
SCHEMA = STANDARD,
DATABASE = 'master',
NAMESPACE = 'http://tempUri.org/'
);
GO
Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Msg 7878, Level 16, State 1, Line 2
This "CREATE ENDPOINT" statement is not supported on this edition of SQL Server.
Actually I was not aware of the ENDPOINT thing so first I search on BOL and find that SOAP is still in 2012 so I post that link...
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
April 12, 2013 at 7:37 am
Mighty (4/12/2013)
Shouldn't TCP in the answers be TSQL?TCP is one of the two protocols that can be used, TSQL is a payload type.
I was wondering this myself. The documentation for creating an endpoint lists TCP as the only protocol you can select. The possible endpoints are listed as { TSQL | SERVICE_BROKER | DATABASE_MIRRORING }.
April 12, 2013 at 10:11 am
Interesting question. Of course none of the answer options is actually correct because the all say TCP where they mean T-SQL but that won't confuse anyone.
It's sort of nice to know that MS isn't changing - BOL still contradicts itself quite regularly. That will confuse people more that almost any QOTD will.
Tom
April 12, 2013 at 11:29 am
from the link:http://msdn.microsoft.com/en-us/library/ms162560.aspx
Implementing Endpoints
SQL Server 2012 Other Versions SQL Server 2008 R2SQL Server 2008SQL Server 2005This topic has not yet been rated - Rate this topic An endpoint is a service that can listen natively for requests. SMO supports various types of endpoints by using the Endpoint object. You can create an endpoint service that handles a specific type of payload, which uses a specific protocol, by creating an instance of an Endpoint object and setting its properties.
The EndpointType property of the Endpoint object can be used to specify on of the following payload types:
•Database mirroring
•SOAP
•Service Broker
•Transact-SQL
Also, the ProtocolType property can be used to specify the following two supported protocols:
•HTTP protocol
•TCP protocol
--------------------------------------
;-)“Everything has beauty, but not everyone sees it.” ― Confucius
April 12, 2013 at 11:31 am
+1. Good question, even had the normal QOTD twist and kink in it.
M.
Not all gray hairs are Dinosaurs!
April 12, 2013 at 11:34 am
L' Eomot Inversé (4/12/2013)
Interesting question. Of course none of the answer options is actually correct because the all say TCP where they mean T-SQL but that won't confuse anyone.It's sort of nice to know that MS isn't changing - BOL still contradicts itself quite regularly. That will confuse people more that almost any QOTD will.
I've corrected this to say TSQL, as I was thinking TSQL and writing TCP incorrectly.
April 12, 2013 at 11:35 am
chgn01 (4/12/2013)
from the link:http://msdn.microsoft.com/en-us/library/ms162560.aspx
That link is incorrect. Bug submitted to Connect: https://connect.microsoft.com/SQLServer/feedback/details/783547/implementing-endpoints-documentation-is-wrong
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply