SQL Server

SharePoint -- Download a Text File into a String Variable

See more SharePoint Examples

Demonstrates how to download a text file from SharePoint into a string variable. 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
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    --  This requires the Chilkat API to have been previously unlocked.
    --  See Global Unlock Sample for sample code.

    --  -------------------------------------------------------------------------
    --  The following comments apply to SharePoint Windows classic authentication.
    --  -------------------------------------------------------------------------
    --  For example, imagine our SharePoint endpoint is https://xyzoffice.mycompany.com/
    --  The SHAREPOINT_NTLM_DOMAIN would be "mycompany.com"
    --  The SHAREPOINT_HTTPS_DOMAIN would be "xyzoffice.mycompany.com"
    --  Also, the SHAREPOINT_USERNAME would be just the name, not a full email address.
    --  for example, "chilkat" instead of "chilkat@mycompany.com"

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

    --  If SharePoint Windows classic authentication is used, then set the 
    --  Login, Password, LoginDomain, and NtlmAuth properties.
    EXEC sp_OASetProperty @http, 'Login', 'SHAREPOINT_USERNAME'
    EXEC sp_OASetProperty @http, 'Password', 'SHAREPOINT_PASSWORD'
    EXEC sp_OASetProperty @http, 'LoginDomain', 'SHAREPOINT_NTLM_DOMAIN'
    EXEC sp_OASetProperty @http, 'NtlmAuth', 1

    --  -------------------------------------------------------------------------
    --  The more common case is to use SharePoint Online authentication (via the SPOIDCRL cookie).
    --  If so, do not set Login, Password, LoginDomain, and NtlmAuth, and instead
    --  establish the cookie as shown at SharePoint Online Authentication
    --  -------------------------------------------------------------------------

    --  This example downloads a CSV file that is utf-8 and contains Japanese characters.

    DECLARE @url nvarchar(4000)
    SELECT @url = 'https://SHAREPOINT_HTTPS_DOMAIN/_api/web/GetFileByServerRelativeUrl(''/Documents/ChilkatTest/japanese.csv'')/$value'

    EXEC sp_OASetProperty @http, 'AcceptCharset', 'utf-8'

    DECLARE @strCsv nvarchar(4000)
    EXEC sp_OAMethod @http, 'QuickGetStr', @strCsv OUT, @url
    EXEC sp_OAGetProperty @http, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        RETURN
      END

    --  The CSV file is contained in strCsv.

    PRINT 'CSV:'

    PRINT @strCsv

    --  Note: The HTTP response hopefully indicates the charset of the response,
    --  and Chilkat should receive the string correctly.  If the response sent by
    --  SharePoint does not indicate a charset, or indicates an incorrect charset,
    --  then we can instead download the text file as binary data and interpret the
    --  bytes ourselves correctly.  For example:  

    DECLARE @bd int
    EXEC @hr = sp_OACreate 'Chilkat.BinData', @bd OUT

    EXEC sp_OAMethod @http, 'QuickGetBd', @success OUT, @url, @bd
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @bd
        RETURN
      END

    --  Interpret the bytes correctly as utf-8
    DECLARE @sb int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sb OUT

    EXEC sp_OAMethod @sb, 'AppendBd', @success OUT, @bd, 'utf-8', 0, 0

    PRINT 'CSV:'
    EXEC sp_OAMethod @sb, 'GetAsString', @sTmp0 OUT
    PRINT @sTmp0

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @bd
    EXEC @hr = sp_OADestroy @sb


END
GO