Demo Data from EDBT 2026 / reviewers in the wild / expert
Shrikanth Shankar
dblp:62/3723
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 2008
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 2
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
2 papers |
Indexing and storage engines · 35% Database system architecture and tuning · 35% Query processing and optimization · 23% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Storage systems · 100% |
Topics — the 3 heaviest of 6, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Indexing and storage engines › partitioning
table partitioning |
0.1 | 1 | 2008 | Supporting table partitioning by reference in oracle · SIGMOD Conference 2008 |
Query processing and optimization
view maintenance |
0.1 | 1 | 2005 | Optimizing Refresh of a Set of Materialized Views · VLDB 2005 |
Storage systems › storage management
information lifecycle management |
0.0 | 1 | 2008 | Supporting table partitioning by reference in oracle · SIGMOD Conference 2008 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2008 | Supporting table partitioning by reference in oracleabstractPartitioning is typically employed on large-scale data to improve manageability, availability, and performance. However, for tables connected by a referential constraint (capturing a parent-child relationship), the current approaches require individually partitioning each table thereby burdening the user with the task of maintaining the tables equi-partitioned, which not only is cumbersome but also error prone. This paper proposes a new partitioning method (partition by reference) that allows tables with a parent-child relationship to be logically equi-partitioned by inheriting the partition key from the parent table without duplicating the key columns. The partitioning key is resolved through an existing parent-child relationship, enforced by an active referential constraint. This logical dependency is used to automatically i) cascade partition maintenance operations performed on parent table to child tables, and ii) handle migration of child rows when partition key or parent key in parent table is updated, as a single atomic operation. This method has been introduced in Oracle Database 11gR1 with support for tables with both single level and composite partitioning methods. The paper describes the key concepts of table partitioning by reference method, discusses the design and implementation challenges, and presents an experimental study covering a usage scenario common in Information Life Cycle Management (ILM) applications. George Eadon, Eugene Inseok Chong, Shrikanth Shankar, Ananth Raghavan, Jagannathan Srinivasan, Souripriya Das |
SIGMOD Conference | 3 |
| 2005 | Optimizing Refresh of a Set of Materialized Views
Nathan Folkert, Abhinav Gupta 0003, Andrew Witkowski, Sankar Subramanian, Srikanth Bellamkonda, Shrikanth Shankar, Tolga Bozkaya |
VLDB | 6 |