Roger S. Barga, David B. Lomet, Thomas Baby, and Sanjay Agrawal. Persistent client-server database sessions. In EDBT Conference, pages 462--477, March 2000. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Phoenix Project: Fault-Tolerant Applications - Roger Barga David (2002) (2 citations) Self-citation (Barga Lomet) (Correct)
....execution semantics. We strictly separate the obligations of a contract from its implementation in terms of logging. We can thus give strong guarantees to the external users while frequently avoiding expensive measures such as forced logging [LoWe98] Persistent Database Sessions via Phoenix ODBC [BL99, BL2000, BL2001] was our first prototype system. It insulates applications from database server failures. It does not provide recovery from client (application) system failures. ODBC Background ODBC (Open Database Connectivity) is a client application API to SQL database servers based on the X Open SQL Call ....
R. Barga, D. Lomet, T. Baby, S. Agrawal. Persistent Client-Server Database Sessions, Conf. on Extending Database Technology, Lake Constance,
Measuring and Optimizing a System for Persistent Database.. - Barga, Lomet Self-citation (Barga Lomet) (Correct)
....from the client application. This persistent database session component, called Phoenix ODBC, is implemented without specialized database system support, and requires no changes to client applications or native ODBC drivers. 1. 2 This Paper s Contribution The role of Phoenix ODBC, as described in [4,5], is to improve application availability by masking database server crashes from a client in as cost effective manner as possible. Our focus in this paper is on quantifying and reducing the impact on application response time and database server throughput. We report on experiments that measure ....
....appropriately. Phoenix ODBC performs three main functions in providing persistent database sessions. To make this paper self contained, we present an overview of each function in the following subsections. Additional details can be found in an earlier paper describing the design of Phoenix ODBC [5]. 2.1 Persisting Volatile Session State Actions that Phoenix ODBC must take to analyze the application request and provide for the persistence of volatile session state are performed by Phoenix, prior to passing the request to the native driver. This approach to providing database sessions that ....
[Article contains additional citation context not shown here]
Barga, R., Lomet, D., Baby, T., and Agrawal, S. Persistent Client-Server Database Sessions. Proceedings of EDBT Conference, Lake Constance, Germany.
Phoenix: Making Applications Robust - Barga, Lomet (1999) (3 citations) Self-citation (Barga Lomet) (Correct)
....identifies the application s last completed request and asks the server to re send the result set if necessary 4. Phoenix ODBC Performance Using queries from the TPC D benchmark, we conducted an evaluation of Phoenix ODBC to measure the costs of persisting and recovering ODBC database sessions[4]. We found the following: Phoenix ODBC overhead to persist result sets for queries with a high degree of complexity, such as those found in the TPC D benchmark, is modest. For benchmark query Q5 the response time difference between Phoenix ODBC and vanilla ODBC is less than 4 , while for query ....
Barga, R.S., and Lomet, D.B. Persistent Client-Server Database Sessions, Feb. 1999, Microsoft Technical Report (submitted).
Unknown - (Correct)
No context found.
Roger S. Barga, David B. Lomet, Thomas Baby, and Sanjay Agrawal. Persistent client-server database sessions. In EDBT Conference, pages 462--477, March 2000.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC