When running SQL Server without a network, you follow the same procedures as if SQL Server were running with a network, except that you don't need to start the built-in Server service. Because SQL Enterprise Manager, SQL Service Manager, and the net start and net stop commands are always functional (even without a network), the procedures for starting and stopping SQL Server are identical for network or standalone operation.
When connecting to a standalone SQL Server from a local client such as isql, you bypass the network and connect directly to the SQL Server using a local pipe. The only difference between a local pipe and a network pipe is whether or not the network is involved ¾ both establish a connection with SQL Server using the standard pipe (\pipe\sql\query) unless otherwise directed.
When you connect to a local SQL Server without specifying a server name, you're using a local pipe. When you connect to a local SQL Server and explicitly specify a server name, you're using either a network pipe or another network IPC mechanism such as IPX/SPX (if you have configured SQL Server to use multiple networks). Because a standalone SQL Server does not support network pipes, you must omit the unnecessary server_name argument when connecting to the SQL Server from a client. For example, to connect to a standalone SQL Server from isql, type:
isql /Usa /P