rp_sqlredirect: Background

With the number of Sybase servers on campus growing, the need has arisen for reliable data transfer between servers. It is not reasonable to assume that every department on campus will use the ACS dataservers as their up-front platforms. Departments expect a way to transport the data from the ACS dataservers to their own for use by their applications, report generators, etc.

Further, the proliferation Sybase SQL servers among ACS has necessitated this type of communication. Since sybase1 is used strictly for transaction-oriented applications (such as Powerbuilder and WWW applications) no extracts are allowed into this server. Since acs_dds is used strictly for extracts aquired from the mainframe, and can be quite heavily used for reporting queries, data may need to be copied from acs_dds to sybase1 or vice versa.

Currently, the only effective means of server-to-server communication using Sybase is through the use of remote procedure calls or RPC's. As an initial attempt at solving the server-to-server problem, ACS has developed a generic RPC that addresses the problem of data transfer between Sybase servers.

This particular RPC is known as rp_sqlredirect and is discussed further within the pages of this document.

Back to the SQL-Redirect Index Page

Last Modified Wednesday, September 25, 1996 - Lou Williams