tag:blogger.com,1999:blog-3617908412741200959.post1143885171824254754..comments2024-03-18T22:03:43.359-07:00Comments on sql.sasquatch: O Registry, Registry! But wherefore did you so much tempt the heavens?SQL_Sasquatchhttp://www.blogger.com/profile/13470482959972282429noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3617908412741200959.post-74706417458798658502013-05-02T16:56:35.843-07:002013-05-02T16:56:35.843-07:00Nope. Would be a great step if my current concern...Nope. Would be a great step if my current concern was connection rejection :) As it happens, I see a small number of unexpected connection rejection and authentication failures occasionally. I'll probably loop back in a few months to try to stamp them out. This post is a sidetrack from researching FCoE failure/diagnosis/correction routes for sustained high disk IO SQL Server workflows. Spent time today reading through 10gbE CNA driver and firmware release notes... looking for TCP timer errors, false-checksum-error packet drops, diagnostics for queue full events... and that's where I sidetracked to Windows registry backlog settings. SQL_Sasquatchhttps://www.blogger.com/profile/13470482959972282429noreply@blogger.comtag:blogger.com,1999:blog-3617908412741200959.post-52717335761797974432013-05-02T08:48:30.127-07:002013-05-02T08:48:30.127-07:00Just out of curiosity, have you considered using p...Just out of curiosity, have you considered using procmon to see if later versions of SqlServer.exe read the registry keys registered mentioned in the older KB articles?zippy1981https://www.blogger.com/profile/15771103697556009092noreply@blogger.com