SQL Server

Set Default NTLM Protocol Version (v1 or v2)

Demonstrates how to set the default NTLM protocol version. 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
    DECLARE @iTmp0 int
    -- The default NTLM protocol version used Chilkat-wide, for any 
    -- operations involving NTLM can be set like this:

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

    -- Choose 1 or 2:
    EXEC sp_OASetProperty @glob1, 'DefaultNtlmVersion', 1

    -- That is all.  The variable named "glob1"
    -- does not need to be kept in existence. 

    -- For example:
    DECLARE @glob2 int
    EXEC @hr = sp_OACreate 'Chilkat.Global', @glob2 OUT

    -- Should show the value 1.

    EXEC sp_OAGetProperty @glob2, 'DefaultNtlmVersion', @iTmp0 OUT
    PRINT 'New NTLM default version: ' + @iTmp0

    -- The Chilkat global object follows the singleton design pattern.
    -- There is only one instance of the global object within Chilkat.
    -- When your program creates a new instance, such as glob1 or glob2,
    -- they are reallly just references to the same singleton object
    -- within Chilkat.

    EXEC @hr = sp_OADestroy @glob1
    EXEC @hr = sp_OADestroy @glob2


END
GO