How to Get a Paper Accepted at a Database Conference

We still remember the first rejection email vividly. It arrived at 3am, just as we were convincing ourselves that no news was good news. The reviews were brutal: “limited novelty,” “evaluation feels rushed,” “unclear positioning against prior work.” Six months later, after a full rewrite and a change of venue, the same core idea was accepted with strong scores — and the feeling of reading “Accept” was worth every late night in between. If you are working on database systems or big data management research, that cycle of rejection and acceptance is not a sign you are doing something wrong. It is the process. In this post, we share what we have learned from submitting to, reviewing for, and attending conferences across the database landscape, and how you can stack the odds in your favour.

Understanding the Database Conference Landscape

Before you write a single line of your paper, you need to know where it belongs. Database research has a well-defined hierarchy, and choosing the right venue is half the battle. Submit a solid but incremental piece of work to a top-tier venue and it may be dismissed; submit it to a specialised conference and it could be a strong contribution.

Top-Tier vs. Specialized Conferences

In our field, SIGMOD and VLDB are considered top-tier database conferences, alongside ICDE. These venues demand significant novelty, rigorous evaluation, and broad impact. They are competitive, with acceptance rates often hovering around 15–25%. Specialised and regional conferences, by contrast, offer a more focused audience and a more forgiving bar for novelty — as long as the work is technically sound and clearly presented.

• SIGMOD – flagship ACM conference, strong emphasis on systems and theory.
• VLDB – large-scale data management, often with a strong industrial track.
• ICDE – broad coverage of data engineering topics.
• DASFAA – Database Systems for Advanced Applications, a leading international conference with a strong Asia-Pacific and global presence.
• Regional and thematic workshops – excellent stepping stones for early-stage work.

The Role of DASFAA and Other Regional Venues

DASFAA is a leading international conference, and we have found it to be an excellent venue for work that sits between incremental and groundbreaking. Its review process is rigorous but constructive, and the community is welcoming to early-career researchers. Regional venues like DASFAA often provide faster feedback cycles and more opportunities to present work in progress, which is invaluable when you are building a publication record.

UK-Specific Considerations: REF and Beyond

If you are based in the UK, the REF (Research Excellence Framework) assesses research quality in higher education, and conference publications can contribute to your institution’s submission — though weighting varies by panel. This means your choice of venue can have career implications beyond the paper itself. Institutions such as the University of Oxford and Imperial College London are prominent UK institutions for database research, and their groups frequently publish at both top-tier and specialised venues. If you are a PhD student or early-career researcher in the UK, aligning your submission strategy with your department’s REF priorities is worth a conversation with your supervisor.

Crafting a Strong Research Paper

A great idea poorly presented will be rejected. A modest idea exceptionally well presented will often be accepted. The structure and clarity of your paper matter as much as the underlying contribution.

Structuring Your Paper for Maximum Impact

We follow a simple rule: every section should answer a question the reviewer is already asking. The abstract answers “why should I care?” The introduction answers “what is new and why is it hard?” The evaluation answers “does it actually work?” Use SQL and big data management examples to ground your motivation — reviewers in our field respond well to concrete query workloads, data volumes, and latency numbers rather than abstract claims.

Demonstrating Novelty in Database Systems

Novelty does not always mean a brand-new algorithm. It can mean a new combination of existing techniques, a new problem formulation, a new evaluation methodology, or a new application domain. When we review papers, we look for a clear statement of what was known before and what this paper adds. If you cannot articulate that in two sentences, the reviewer will not find it either.

Writing a Compelling Abstract and Introduction

The abstract and introduction are where most papers are won or lost. We recommend drafting the introduction first, then condensing it into the abstract. Avoid vague claims like “big data is growing rapidly.” Instead, state the specific problem, the specific limitation of prior work, and the specific contribution of your paper. SQL remains a fundamental language in database systems and data analytics, so if your work touches query processing or analytics, make that connection explicit early.

Navigating the Submission and Review Process

Submission is not a single event; it is a multi-stage process with distinct deadlines and expectations. Missing a formatting requirement or a rebuttal window can undo months of work.

Meeting Deadlines and Formatting Requirements

Every conference has its own template, page limit, and submission system. We keep a shared checklist that includes:

1. Abstract registration deadline (often a week before the full paper deadline).
2. Formatting template and page limits, including references.
3. Anonymisation requirements for double-blind review.
4. Supplementary material and reproducibility artefacts.
5. Ethics and conflict-of-interest declarations.

Understanding the Review Criteria

Most database conferences evaluate on novelty, technical soundness, evaluation quality, clarity, and relevance. Reviewers are busy, and they often read your paper once before forming an opinion. Make it easy for them: clear figures, well-labelled axes, and a contributions list at the end of the introduction.

Writing an Effective Rebuttal

The rebuttal is your only chance to correct misunderstandings. We keep ours short, structured, and polite. Address the most serious concerns first, provide evidence where possible, and avoid defensive language. If a reviewer has misunderstood something, the fault is usually in the paper, not the reviewer — say so, and commit to fixing it in the camera-ready version.

Learning from Rejections and Iterating

Rejection is data. It tells you something about how your work is perceived, and it is almost always fixable.

Decoding Reviewer Comments

Not all reviewer comments are equally weighted. We sort them into three buckets: fatal flaws (methodology, evaluation, novelty), presentation issues (clarity, structure, figures), and misunderstandings (often a sign of unclear writing). Address the first bucket before resubmitting; the second and third can often be resolved with a careful rewrite.

Revising and Resubmitting

A rejected paper is rarely a dead paper. We have resubmitted papers two or three times before acceptance, each time with a stronger evaluation and clearer positioning. Keep a version history and a response document so you can track what changed and why.

When to Consider a Different Venue

If the core contribution is sound but the venue’s scope does not fit, move on. A paper on data analytics for a niche domain may fare better at a specialised workshop than at SIGMOD. DASFAA and similar venues are often a better home for work that is solid but not paradigm-shifting.

Building a Sustainable Research Pipeline

Publishing is not a one-off event. The researchers who succeed over the long term treat it as a pipeline: multiple projects at different stages, a network of collaborators, and a habit of continuous learning.

Networking at Conferences and Workshops

We make a point of attending at least one UK-based conference or workshop each year, including events hosted at institutions such as the University of Oxford and Imperial College London. These gatherings are where collaborations start and where you hear about problems before they appear in print.

Collaborating with Peers and Mentors

Co-authorship is one of the fastest ways to improve your writing and your research taste. Work with someone who has published at your target venue, and ask them to critique your drafts before submission.

Staying Updated with Database Systems Research

Follow the proceedings of SIGMOD, VLDB, ICDE, and DASFAA. Read the papers that get best-paper awards and try to understand what made them stand out. Over time, this builds an intuition for what the community values.

FAQ

How long does it typically take to get a database paper accepted?

From first submission to acceptance, most researchers we know take between six and eighteen months, often involving one or two rejections and resubmissions. Planning for that timeline reduces frustration.

Is DASFAA a good venue for a first paper?

Yes. DASFAA is a leading international conference with a constructive review culture, and it is a strong choice for early-career researchers who want rigorous feedback without the extreme competitiveness of SIGMOD or VLDB.

Do UK REF rankings really affect where I should submit?

The REF assesses research quality in higher education, and while conference publications can contribute, weightings vary. Check with your department, but never let REF alone dictate your venue choice — fit and audience matter more.

How important is reproducibility in database papers?

Increasingly important. Many venues now offer reproducibility badges, and reviewers reward papers that provide code, datasets, and clear experimental setups. If your work involves SQL or big data management, include the queries and configurations you used.

What is the single biggest mistake authors make?

Failing to clearly state the contribution. If a reviewer cannot summarise your novelty in one sentence after reading the introduction, the paper is likely to be rejected regardless of how good the underlying work is.

Getting a paper accepted at a database conference is rarely about a single brilliant idea. It is about persistence, community engagement, and iterative improvement. Choose your venue carefully, write for the reviewer, learn from every rejection, and keep building your pipeline. The acceptance email will come — and when it does, you will understand exactly why the journey was worth it.