|This utility has been deprecated in Microsoft SQL Server 2005.|
The readpipe utility tests the integrity of the network Named Pipe services, in conjunction with makepipe.
- /S server_name
Is the name of a default instance of Microsoft SQL Server on which you just ran makepipe. readpipe does not support named instances of Microsoft SQL Server 2000. There are no spaces between /S and server_name.
- /D string
Is a test character string. There are no spaces between /D and string.
Specifies the number of iterations.
Queries for incoming data (polling). Without /q, readpipe reads the pipe and waits for data.
Specifies the wait time, in seconds, to pause while polling. The default is 0.
Asks for Transact-SQL named pipes. This option overrides polling.
- /p pipe_name
Is the name of the pipe. The default pipe_name is abc.
This diagnostic utility checks to see if the named pipes are working. Use it (along with makepipe) if you cannot connect to an instance of SQL Server.
Because applications for Microsoft Windows NT, Microsoft Windows, and Win32 Command Prompt all run on Windows NT, you must be careful about which version of makepipe and readpipe you are running. You must use the version specific to the operating system on which you are testing the integrity of the named pipe.
After makepipe is started, the server waits for a client to connect. The readpipe command prompt utility can then be run from other workstations. When all testing is complete, go to the screen where the makepipe utility is running and press CTRL+BREAK or CTRL+C to stop execution.
The readpipe utility is not installed by SQL Server Setup. The utility can be found in the x:\x86\Binn directory on the SQL Server compact disc.