SQLTrace tool has a defect regarding BID trace of MSODBCSQL13 and MSODBCSQL11

Open Beginner friendly
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
powershell
Domain
databases, tooling

Research direction

Open SQLTrace.ps1 and locate the hard-coded GUID values used for the MSODBCSQL11 and MSODBCSQL13 BID traces. Replace them with the GUIDs listed in the issue, then verify that the SQLTrace tool can capture BID traces successfully for both driver versions.

Written by the indexing model from the issue text.

Description

For the SQLTrace tool, I noticed a defect: the SQLTrace.ps1 hard code the incorrect guid for MSODBCSQL13 and MSODBCSQL11.

The MSODBCSQL11 guid should be edafc39f-b768-36db-8a5b-24a02176bfa9 instead of 7C360F7F-7102-250A-A233-F9BEBB9875C2
The MSODBCSQL13 guid should be 06debc35-76ab-2719-2abe-e7e57f1dad2c instead of 85DC6E48-9394-F805-45C9-C8B2ACA2E7FE

This defect can make CSS engineers cannot capture the BID trace for MSODBCSQL11 and MSODBCSQL13 successfully. Please kindly aware this defect and plan to fix it. Thanks a lot.

Dominant language
C#
Stars
209
Forks
59
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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/CSS_SQL_Networking_Tools

All issues in microsoft/CSS_SQL_Networking_Tools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.