Replication Topology Report Showing Wrong Results

Open
  • Is something wrong?
#441 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp, sql
Domain
databases

Research direction

Open NexusReports/Replication_Topology_C.rdl around line 20 and inspect the report query. Run the query in SSMS with the scenario from the issue to reproduce the Cartesian join. Done means the replication topology report lists only subscriptions that actually exist for each publisher.

Written by the indexing model from the issue text.

Description

The replication topology report is showing wrong results on some situations. In the scenario below, it lists some subscriptions that don’t exist for the given publisher because of a Cartesian join, showing combinations that don't exist

Image

Confirmed the issue is in the query used by the report design. We see the same cartesian join if we run it directly on SSMS

https://github.com/microsoft/SqlNexus/blob/b8b78f3cb0a3da37d701148942cc5a3768c61c2e/NexusReports/Replication_Topology_C.rdl#L20

Dominant language
C#
Stars
436
Forks
111
Avg merge
2d 9h
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/SqlNexus

All issues in microsoft/SqlNexus

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.