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
Demo Data from EDBT 2026 / reviewers in the wild / expert

Brad Hammond

dblp:30/3192 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 1999
—ORCID · none

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

Databases, data management, data science and information retrieval · 2 · 2 first-author

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
Distributed and cloud data management · 89% Database theory · 11%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

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

TopicWeightPapersLastEvidence papers
Distributed and cloud data management
data replication		 0.021999
Merge Replication in Microsoft's SQL Server 7.0 · SIGMOD Conference 1999
Using Referential Integrity To Easily Define Consistent Subset Replicas · VLDB 1996
Distributed systems › distributed coordination
conflict resolution		 0.011999
Merge Replication in Microsoft's SQL Server 7.0 · SIGMOD Conference 1999
Distributed systems
replication		 0.011999
Merge Replication in Microsoft's SQL Server 7.0 · SIGMOD Conference 1999
Database theory › integrity constraints
referential integrity		 0.011996
Using Referential Integrity To Easily Define Consistent Subset Replicas · VLDB 1996
YearPublicationVenuePosition
1999 Merge Replication in Microsoft's SQL Server 7.0
abstract
SQL Server 7.0 offers three different styles of replication that we call Transactional Replication, Snapshot Replication, and Merge Replication. Merge Replication means that data changes can be performed at any replica, and that the changes performed at multiple replicas are later merged together. Because Merge Replication allows updates to disconnected replicas, it is particularly well suited to applications that require a lot of autonomy. A special process called the Merge Agent propagates changes between replicas, filters data as appropriate, and detects and handles conflicts according to user-specified rules.
Brad Hammond
 SIGMOD Conference1
1996 Using Referential Integrity To Easily Define Consistent Subset Replicas
Brad Hammond
 VLDB1