SQL Server

Example: Http.CloseAllConnections method

See more HTTP Examples

Demonstrates how to call the CloseAllConnections method. SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Demonstrate 
    DECLARE @url nvarchar(4000)
    SELECT @url = 'https://finnhub.io/api/v1/quote?symbol={$symbol}&token={$api_key}'

    -- When the request is sent, the {$symbol} is replaced with "MSFT"
    -- and the {$api_key} is replaced with "1234567890ABCDEF"
    EXEC sp_OAMethod @http, 'SetUrlVar', @success OUT, 'symbol', 'MSFT'
    EXEC sp_OAMethod @http, 'SetUrlVar', @success OUT, 'api_key', '1234567890ABCDEF'

    DECLARE @sbJson int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbJson OUT

    EXEC sp_OAMethod @http, 'QuickGetSb', @success OUT, @url, @sbJson
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @sbJson
        RETURN
      END

    DECLARE @statusCode int
    EXEC sp_OAGetProperty @http, 'LastStatus', @statusCode OUT
    EXEC sp_OAGetProperty @http, 'LastResponseHeader', @sTmp0 OUT
    PRINT @sTmp0

    -- The response header contains this:

    -- Date: Tue, 19 Aug 2025 12:18:56 GMT
    -- Content-Type: application/json; charset=utf-8
    -- Transfer-Encoding: chunked
    -- Connection: keep-alive
    -- Content-Encoding: gzip

    -- The "Connection: keep-alive" header ensures the server keeps the connection open for subsequent requests.
    -- If the server responds with a "Connection: close" header, it indicates the connection will be closed after the response. 
    -- Consequently, Chilkat will also close the connection, requiring a new one to be established for any subsequent requests to the same server.

    -- If your application uses the same HTTP object instance to send requests to a different server, a new connection will be established with that server.
    -- Existing connections remain open, with Chilkat maintaining up to 10 open connections. 
    -- If all 10 connections are in use, Chilkat will close the least recently used connection to connect to a new server.

    -- Your application can explicitly close all open connections like this:
    EXEC sp_OAMethod @http, 'CloseAllConnections', @success OUT
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @sbJson
        RETURN
      END


    PRINT 'Success.'

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @sbJson


END
GO