microsoft / microsoft/CSS_SQL_Networking_Tools
SQLTrace tool has a defect regarding BID trace of MSODBCSQL13 and MSODBCSQL11
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 209
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
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 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.
Assessment
- Tech stack
- powershell
- Domain
- databases, tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 64/100