SQL Server
SQL Server
FTPS / Implicit SSL
See more FTP Examples
Demonstrates how to connect using implicit SSL on port 990. The FTP component connects using SSL on port 990, which is the de-facto standard FTP SSL port. Not all FTP servers support implicit SSL. An alternative is to use AUTH SSL (also called AUTH TLS).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
-- 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 requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
DECLARE @ftp int
EXEC @hr = sp_OACreate 'Chilkat.Ftp2', @ftp OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- If this example does not work, try using passive mode
-- by setting this to 1.
EXEC sp_OASetProperty @ftp, 'Passive', 0
EXEC sp_OASetProperty @ftp, 'Hostname', 'ftp.something.com'
EXEC sp_OASetProperty @ftp, 'Username', 'test'
EXEC sp_OASetProperty @ftp, 'Password', 'test'
EXEC sp_OASetProperty @ftp, 'Port', 990
-- We don't want AUTH SSL:
EXEC sp_OASetProperty @ftp, 'AuthTls', 0
-- We want Implicit SSL:
EXEC sp_OASetProperty @ftp, 'Ssl', 1
-- Connect and login to the FTP server.
EXEC sp_OAMethod @ftp, 'Connect', @success OUT
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ftp
RETURN
END
ELSE
BEGIN
-- LastErrorText contains information even when
-- successful. This allows you to visually verify
-- that the secure connection actually occurred.
EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
END
PRINT 'FTPS Channel Established!'
-- Do whatever you're doing to do ...
-- upload files, download files, etc...
EXEC sp_OAMethod @ftp, 'Disconnect', @success OUT
EXEC @hr = sp_OADestroy @ftp
END
GO