microsoft / microsoft/SqlNexus
Replication Topology Report Showing Wrong Results
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 427
- Forks
- 111
- Avg merge
- 3d 42m
- Merged PRs (30d)
- 8
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
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100