MSSQL Response Time for SQL DB hosts due to Npcap 1.31
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
- We are querying where time_taken (response time) > 10 seconds for SQL DB hosts with Npcap 1.31.
- You can see a big spike every hour of 100+ events which goes up depending on how busy our system is.
- You can't tell from here but the time increments by 30 seconds each hour.
- The other indicator is when we get cluster disconnect errors in the SQL Server event log. We have 5 servers in a cluster hosting the database, and this error indicates they timed out on their heartbeat connection. These don’t happen every hour, just several times per day but they happen at the times when the slowness happens.
- Upgrading from the Winpcap driver to an Npcap driver has still not resolved our issue
- Initially, the spikes correlated with metric reporting time so we changed the interval to test and nothing changed.
- After removing all core components without success, we removed the pcap driver entirely, and the issue went away.
Diagnostic information
Windows Server 2016 Standard 1607, ver. 10.0.14393
Additional context
Attached DiagReport, Install.log, and NPFInstall log
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
Review the attached DiagReport, Install.log, and NPFInstall log first, comparing the hourly response-time spikes and SQL Server cluster disconnects with the Npcap installation details. Reproduce the behavior on Windows Server 2016 with the Npcap driver and confirm that removing the pcap driver eliminates it; done means identifying and correcting the driver-related cause without disrupting SQL connectivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sql
- Domain
- databases, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100