SQL Server
SQL Server
Connect to a REST Server
See more REST Examples
Demonstrates Rest.Connect, which establishes the initial TCP (and optionally TLS) connection to a REST server. The example connects over HTTPS and then reuses the connection for a request.
Background. A single connection can serve many requests to the same host. The TLS argument should be
_TRUE_ for HTTPS (typically port 443), and automatic reconnection lets Chilkat transparently re-establish a dropped keep-alive connection.Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
DECLARE @rest int
EXEC @hr = sp_OACreate 'Chilkat.Rest', @rest OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Connect to the REST server. The 3rd argument enables TLS (use 1 for HTTPS on port 443),
-- and the 4th enables automatic reconnection if the connection is dropped between requests.
DECLARE @bTls int
SELECT @bTls = 1
DECLARE @bAutoReconnect int
SELECT @bAutoReconnect = 1
EXEC sp_OAMethod @rest, 'Connect', @success OUT, 'example.com', 443, @bTls, @bAutoReconnect
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
RETURN
END
-- The connection is now established and ready for requests. A single connection can be reused for
-- many requests to the same server.
DECLARE @responseText nvarchar(4000)
EXEC sp_OAMethod @rest, 'FullRequestNoBody', @responseText OUT, 'GET', '/api/status'
EXEC sp_OAGetProperty @rest, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 = 0
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
RETURN
END
PRINT @responseText
EXEC @hr = sp_OADestroy @rest
END
GO