Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!xanth!mcnc!rti!xyzzy!aquila.DG.COM!harrism From: harrism@aquila.DG.COM (Mike Harris) Newsgroups: comp.databases Subject: Re: Client/Server processes and implementations Keywords: Client Server Processes Message-ID: <717@xyzzy.UUCP> Date: 28 Nov 89 13:58:43 GMT References: <7189@sybase.sybase.com> <7114@sybase.sybase.com> <6895@sybase.sybase.com> <2184@kodak.UUCP> <375@xyzzy.UUCP> <510@xyzzy.UUCP> <7185@sybase.sybase.com> Sender: usenet@xyzzy.UUCP Lines: 23 In article <7189@sybase.sybase.com>, coop@phobos.sybase.com (John Cooper) writes: > My colleague Jon Forrest neglected to mention what RPC's are. For those not > familiar with Sybase this stands for Remote Procedure Calls. As of version > 4.0 of our SQL-Server, we offer the ability for a user in one server to call a > stored procedure remotely in another server. > It should be made clear that these are Data Base RPCs. An RPC is a generic term relating to any Remote Procedure Call. It can be against a database, as in stored procecures, or against remote language subroutine code (such as C ), etc. It, by default, indicates the calling of a remote language procedure, such as C, not a database stored procedure. > I believe Sybase is the only RDBMS that has stored procedures. > Several other companies, DG's DG/SQL for instance, provide pre compilation, statement caching, database resident SQL code, etc. This is an area where apples & oranges are in the same basket & the gains received by them are goverened by the procducts overall architecture & how it is complemented. > John Cooper | My opinions, may not be employer's. regards, Mike Harris - KM4UL harrism@dg-rtp.dg.com Data General Corporation {world}!mcnc!rti!dg-rtp!harrism Research Triangle Park, NC Brought to you by Super Global Mega Corp .com