Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Srinivasa Narayanan

dblp:18/1813 · DBLP profile ↗
← Back
5ranked-venue papers
1as first author
0since 2021 · last 2005
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 4 · 1 first-authorSoftware engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
3 papers
Data models and query languages · 67% Database system architecture and tuning · 33%

Topics — the 2 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Data models and query languages
object-relational database
0.011999
O-O, What Have They Done to DB2? · VLDB 1999
Data models and query languages › object-relational database
object-relational data model
0.011999
O-O, What's Happening to DB2? · SIGMOD Conference 1999
YearPublicationVenuePosition
2005 SOA in the Real World - Experiences
Manoj Acharya, Abhijit Kulkarni, Rajesh Kuppili, Rohit Mani, Nitin More, Srinivasa Narayanan, Parthiv Patel, Kenneth W. Schuelke, Iyer N. Subramanian
ICSOC6
2001 Tavant System Architecture for Sell-side Channel Management
Srinivasa Narayanan, Iyer N. Subramanian
VLDB1
1999 O-O, What's Happening to DB2?
abstract
In this presentation, we will describe a collection of new object-relational features that have been added to IBM's DB2 Universal Database (UDB) system. The features to be described include support for structured types, object references, and hierarchies of typed tables and views. These features will be covered from the perspective of a database designer or end user. In addition to presenting the features presently available in DB2 UDB V5.2, which became available in Fall 1998, we will discuss the expected evolution and impact of this technology over time.
Michael J. Carey 0001, Donald D. Chamberlin, Srinivasa Narayanan, Bennet Vance, Doug Doole, Serge Rielau, Richard Swagerman, Nelson Mendonça Mattos
SIGMOD Conference3
1999 O-O, What Have They Done to DB2?
Michael J. Carey 0001, Donald D. Chamberlin, Srinivasa Narayanan, Bennet Vance, Doug Doole, Serge Rielau, Richard Swagerman, Nelson Mendonça Mattos
VLDB3
1996 Implementation of a Real-Time Database System
abstract
A real-time database system is a database system in which transactions have explicit timing constraints such as deadlines. Apart from satisfying the database consistency constraints, transaction executions must also satisfy these timing constraints. The goal of transaction and query processing in real-time databases is to maximise the number of successful transactions in the system. This paper reports on the design, development and performance evaluation of RT-Genesis, a real-time database management system resulting from modifying an existing commercial DBMS, Genesis. RT-Genesis is a relational database management system that accommodates SQL queries and transactions having time constraints. It features time-cognizant algorithms for scheduling, concurrency control and buffer management. The system has been tested and the performance of the different algorithms compared in isolation as well as in combination with different classes of SQL workloads. In addition, a two-phased approach to transaction execution has also been implemented with the goal of exploiting access invariance to improve predictability. This work demonstrates the feasibility of converting non-real-time DBMSs into real-time DBMSs for firm deadline transactions. Besides reporting on how this was achieved and on the performance of the incorporated algorithms, lessons learned from this experience are also discussed.
Rohan F. M. Aranha, Venkatesh Ganti, Srinivasa Narayanan, C. R. Muthukrishnan, S. T. S. Prasad, Krithi Ramamritham
Inf. Syst.3