microsoft / microsoft/CSS_SQL_Networking_Tools
SQLCHECK & SSPICLIENT - Feature Request - Sanity check @@SERVERNAME is equivalent to the requested name
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 209
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
I have been banging my head against the wall for hours trying to figure out why SSPI connections to MS SQL servers suddenly started to fail.
From a blind guess troubleshooting from a completely different direction I found out that the @@SERVERNAME property of the MS SQL server/services/instance was different than what was being contacted in the client.
Knowing this would have saved me a lot of pain and it's something I believe the tools should be able to figure out. At the very least SQLCHECK -- SSPICLIENT may be a different story.
If you need clarification please let me know.
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 by reviewing the SQLCHECK and SSPICLIENT entry points that handle SSPI connections and server-name information. Determine how a requested server name can be compared with the SQL Server @@SERVERNAME value, and consider the work complete when the tools clearly report a mismatch; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- authentication, databases, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100