SQL Server >> remote system call?

by Red » Fri, 17 Sep 2004 04:38:24 GMT

Hi all,
I want to be able to have a stored procedure on server A to call a
stored procedure on Server B. I have my stored procedures in place. I have
used Linked servers on server A to define Server B so, that server A can
talk to server B. However I seem to have missed something. This is the
message that I get:
Could not find stored procedure 'sp_tt_load'.(42000,2812)
Procedure(sp_tt_dumpandload_for_standby).


sp_tt_dumpandload_for_standby (server A) does a database dump and then calls
sp_tt_load ( server B). Server B will load the dump onto it's standby
database.

TIA for all the help.

Red




SQL Server >> remote system call?

by Mary Bray » Fri, 17 Sep 2004 05:14:02 GMT


make sure you are using the full name to call the proc including the owner
name eg:
ServerB.databasename.dbo.sp_tt_load



have
calls





SQL Server >> remote system call?

by Red » Fri, 17 Sep 2004 05:40:57 GMT

Thanks Mary, for the advise.

Actually, I found the error in my linked server configuration.

I had defined it using 'other data source' of Microsoft OLE DB provider for
SQL Server.
I should have used 'SQL Server' and then name the server.
Once I changed this, then I was able to make the stored procedure call,
which looks like this:


exec SERVERB...sp_tt_db_load













remote system call?

by Adrian Edwards » Fri, 17 Sep 2004 21:39:50 GMT

Lookup four part naming conventions which should help.
[server].[catalog].[owner].[object]

Adrian






Similar Threads

1. calling a remote SP call that returns a cursor - SQL Server

2. CALL System.Microsoft.AnalysisServices.System.DataMining.Clustering.GetClusterCharacteristics

I did a trace while using the data mining viewers and this MDX is what it's running to get the cluster characteristics:

CALL System.Microsoft.AnalysisServices.System.DataMining.Clustering.GetClusterCharacteristics('Customer Clusters','',0.0005)

The following DMX is somewhat close:

select flattened node_distribution FROM [Customer Clusters].CONTENT where node_name = '000'

Can anyone explain why the DMX differs for continuous values? It appears you don't see all the discrete values from a continuous attribute. Also, how is the Frequency column in that first query calculated? Frequency just appears to be probability except for continuous values.

3. Create Remote Views by Calling dbo.Function()

4. calling a remote command from a sql stored procedures

Hi , i'm trying to run a remote command (or run a program) on an as400
machine (which is successfully added as a linked server) from within an
ms sql server2000 stored procedure..... I tried using rmtcmd with
xp_cmdshell like this

exec master..xp_cmdshell  'rmtcmd CLRPFM FILE(Z8IDFCPYC/TRIAL1)'

but i get the folloowing error:
"CWB4004 - Security error occurred for system "
which means as i guess that the username and password are not sent to
the remote system, although when i run the same command from the
command line it executes successfully wihtout promting for login(client
access is using a default user to connect)  ,so what's the problem ? is
there another way to run a remote command from a stored procedure
?........

5. The incoming tabular data stream (TDS) remote procedure call (RPC)

6. calling remote procedure

Working on MsSQL server I'm calling remote procedure on linked server (Sybase).
like this 
exec BILLING.billing.adm.test

MsSQL returns:
Server: Msg 7212, Level 17, State 1, Line 1
Could not execute procedure 'test' on remote server 'BILLING'.
[OLE/DB provider returned message: [DataDirect][ODBC Sybase Wire Protocol 
driver][SQL Server]Incorrect syntax near '?'.

What does it mean '?'.
There was no mention of symbol ?.

Does anybody know what is it? And how to solve it?
Regards.

7. Error 7391 when inserting remote sp call results

8. MSDTC Time out on Linked Server Remote Procedure Call

I have a pretty simple question.  How do you extended the time out value for 
remote procedure calls between linked servers?  Currently I have a process 
that times out and gives me an information message in the application log 
4156:String message: Session idle timeout over, tearing down the session.  
This process used to work fine but the size of the operation has grown 
overtime and it now takes longer to run then it used to.