microsoft / microsoft/CSS_SQL_Networking_Tools
SQLCheck
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 209
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we only suggest SPNs based on specific SQL installations, basically as found in the log and based on enabled protocols (Named Pipes and/or TCP). I propose we do some additional checks and, if we detect a SQL Alias or AG listener, we suggest those SPNs as well.
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
Start at the SQLCheck entry point and trace the current SPN suggestions based on logged SQL installations and enabled Named Pipes or TCP protocols. Determine how SQL Alias and AG listener detections can feed the same suggestions. Done means those detected aliases and listeners also produce their corresponding SPNs without changing existing suggestions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100