SQL Server
SQL Server
Send Text on an SSH Channel
See more SSH Examples
Demonstrates the Chilkat Ssh.ChannelSendString method, which encodes text using a charset and sends the resulting bytes on a channel. The arguments are the channel number, the text, and the charset. No line ending or terminator is added automatically.
Background: This is how you type into a remote shell programmatically. The most common mistake is forgetting the newline — the remote shell will not act on a command until it receives one, so the terminator must be part of the text you send. An empty string is valid and sends zero bytes. The charset governs how the text becomes bytes on the wire.
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
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- Demonstrates the Ssh.ChannelSendString method, which encodes text with a charset and sends
-- the bytes on a channel. The 1st argument is the channel number, the 2nd is the text, and the
-- 3rd is the charset. No line ending is added automatically.
DECLARE @ssh int
EXEC @hr = sp_OACreate 'Chilkat.Ssh', @ssh OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
DECLARE @sshPort int
SELECT @sshPort = 22
EXEC sp_OAMethod @ssh, 'Connect', @success OUT, 'ssh.example.com', @sshPort
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
-- Normally you would not hard-code the password in source. You should instead obtain it
-- from an interactive prompt, environment variable, or a secrets vault.
DECLARE @password nvarchar(4000)
SELECT @password = 'mySshPassword'
EXEC sp_OAMethod @ssh, 'AuthenticatePw', @success OUT, 'mySshLogin', @password
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
DECLARE @channelNum int
EXEC sp_OAMethod @ssh, 'OpenSessionChannel', @channelNum OUT
IF @channelNum < 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
-- Start a shell WITHOUT requesting a PTY. Without a PTY the shell sees it is connected to a
-- raw data pipe and enters non-interactive mode: it suppresses the command prompt, does not
-- echo typed commands back, and skips interactive login scripts. The output is therefore
-- clean and easily parseable -- but because no prompt is ever sent, code must not wait for
-- one. Instead, have each command print a predictable marker, or wait for EOF / channel close.
EXEC sp_OAMethod @ssh, 'SendReqShell', @success OUT, @channelNum
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
-- Send a command. The trailing newline must be included because no terminator is added.
EXEC sp_OAMethod @ssh, 'ChannelSendString', @success OUT, @channelNum, 'ls -l /tmp' + CHAR(10), 'utf-8'
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
-- Read the shell's response.
DECLARE @pollTimeoutMs int
SELECT @pollTimeoutMs = 2000
DECLARE @result int
EXEC sp_OAMethod @ssh, 'ChannelReadAndPoll', @result OUT, @channelNum, @pollTimeoutMs
IF @result = -1
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
DECLARE @output nvarchar(4000)
EXEC sp_OAMethod @ssh, 'GetReceivedText', @output OUT, @channelNum, 'utf-8'
EXEC sp_OAGetProperty @ssh, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
PRINT @output
EXEC sp_OAMethod @ssh, 'Disconnect', NULL
EXEC @hr = sp_OADestroy @ssh
END
GO