SQL Server
SQL Server
SFTP Upload from Local Filesystem
See more SFTP Examples
Demonstrates how to upload a file to an SSH server. There are no limitations on file size, and the file is streamed directly from the local filesystem.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
-- Important: Do not use nvarchar(max). See the warning about using nvarchar(max).
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- This example assumes the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
DECLARE @sftp int
EXEC @hr = sp_OACreate 'Chilkat.SFtp', @sftp OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Set some timeouts, in milliseconds:
EXEC sp_OASetProperty @sftp, 'ConnectTimeoutMs', 5000
EXEC sp_OASetProperty @sftp, 'IdleTimeoutMs', 10000
-- Connect to the SSH server.
-- The standard SSH port = 22
-- The hostname may be a hostname or IP address.
DECLARE @hostname nvarchar(4000)
SELECT @hostname = 'sftp.example.com'
DECLARE @port int
SELECT @port = 22
EXEC sp_OAMethod @sftp, 'Connect', @success OUT, @hostname, @port
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @sftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @sftp
RETURN
END
-- Authenticate with the SSH server. Chilkat SFTP supports
-- both password-based authenication as well as public-key
-- authentication. This example uses password authenication.
EXEC sp_OAMethod @sftp, 'AuthenticatePw', @success OUT, 'myLogin', 'myPassword'
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @sftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @sftp
RETURN
END
-- After authenticating, the SFTP subsystem must be initialized:
EXEC sp_OAMethod @sftp, 'InitializeSftp', @success OUT
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @sftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @sftp
RETURN
END
-- Open a file for writing on the SSH server.
-- If the file already exists, it is overwritten.
-- (Specify "createNew" instead of "createTruncate" to
-- prevent overwriting existing files.)
DECLARE @handle nvarchar(4000)
EXEC sp_OAMethod @sftp, 'OpenFile', @handle OUT, 'hamlet.xml', 'writeOnly', 'createTruncate'
EXEC sp_OAGetProperty @sftp, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 <> 1
BEGIN
EXEC sp_OAGetProperty @sftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @sftp
RETURN
END
-- Upload from the local file to the SSH server.
EXEC sp_OAMethod @sftp, 'UploadFile', @success OUT, @handle, 'c:/temp/hamlet.xml'
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @sftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @sftp
RETURN
END
-- -----------------------------------------------------------------------------
-- This is important. You must close the handle on the server.
-- Otherwise open handles will accumulate on the server until eventually a limit
-- is reached and the server will fail on a call to OpenFile.
-- -----------------------------------------------------------------------------
-- Close the file.
EXEC sp_OAMethod @sftp, 'CloseHandle', @success OUT, @handle
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @sftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @sftp
RETURN
END
PRINT 'Success.'
EXEC @hr = sp_OADestroy @sftp
END
GO