dotnet / dotnet/SqlClient

Document SQL Server Named Pipes configuration for tests

Open
#3,192 8 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
989
Forks
340
Avg merge
4d 19h
Merged PRs (30d)
72

Description

SqlClient can use TCP or Named pipes to connect to the sql server and there are tests that are forced to run on each protocol to make sure they work. In order to have the tests run a connection string must be provided and named pipes must be configured on the test machine and sql server machine.

But how? In the past I had assumed that my installation of SQL Server had somehow been broken or misconfigured by me but i've recently done a complete new build on new hardware and yet named pipes still do not work locally for me. I've spent time in the past looking into why and got nowhere.

In order to have named pipe specific tests run correctly locally i need to be able to correctly configure the sql server, local named pipe client and test json file. Can exact instructions from a clean install of SQL Server and Windows be provided to help with this please?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.