Skip to content

run-sql-server-with-or-without-a-network.md

Latest commit

 

History

History
52 lines (40 loc) · 3.94 KB

run-sql-server-with-or-without-a-network.md

File metadata and controls

52 lines (40 loc) · 3.94 KB
title Run SQL Server with or Without a Network
description Learn how to run SQL Server on a network and without one. For local use, see how to use a local pipe. For network use, see how to check for required services.
author rwestMSFT
ms.author randolphwest
ms.date 08/26/2025
ms.service sql
ms.subservice configuration
ms.topic conceptual
helpviewer_keywords
verifying Server service has been started
net start [SQL Server]
command prompt [SQL Server], connections
SQL Server services, networks
status information [SQL Server], Server service
running SQL Server
networking [SQL Server], SQL Server with or without
services [SQL Server], networks
starting Server service
SQL Server, running

Run SQL Server with or without a network

[!INCLUDE SQL Server]

[!INCLUDE ssNoVersion] can run on a network, or it can function without a network.

Run SQL Server on a network

For [!INCLUDE ssNoVersion] to communicate over a network, the [!INCLUDE ssNoVersion] service must be running. By default, Windows automatically starts the built-in [!INCLUDE ssNoVersion] service. To find out whether the [!INCLUDE ssNoVersion] service has started, at the command prompt, type the following command:

net start

If the services associated with [!INCLUDE ssNoVersion] have been started, the following services appear in the net start output:

  • Analysis Services (MSSQLSERVER)
  • SQL Server (MSSQLSERVER)
  • SQL Server Agent (MSSQLSERVER)

Run SQL Server without a network

When running an instance of [!INCLUDE ssNoVersion] without a network, you don't need to start the built-in [!INCLUDE ssNoVersion] service. Because [!INCLUDE ssManStudioFull], SQL Server Configuration Manager, and the net start and net stop commands are functional even without a network, the procedures for starting and stopping an instance of [!INCLUDE ssNoVersion] are identical for a network or stand-alone operation.

When connecting to an instance of a stand-alone [!INCLUDE ssNoVersion] from a local client such as sqlcmd, you bypass the network and connect directly to the instance of [!INCLUDE ssNoVersion] by using a local pipe. The difference between a local pipe and a network pipe is whether you're using a network. Both local and network pipes establish a connection with an instance of [!INCLUDE ssNoVersion] by using the standard pipe (\\.\pipe\sql\query), unless otherwise directed.

When you connect to an instance of a local [!INCLUDE ssNoVersion] without specifying a server name, you're using a local pipe. When you connect to an instance of a local [!INCLUDE ssNoVersion] and specify a server name explicitly, you're using either a network pipe or another network interprocess communication (IPC) mechanism, such as Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) (assuming you configured [!INCLUDE ssNoVersion] to use multiple networks). Because a stand-alone [!INCLUDE ssNoVersion] doesn't support network pipes, you must omit the unnecessary /<Server_name> argument when connecting to the instance of [!INCLUDE ssNoVersion] from a client. For example, to connect to a stand-alone instance of [!INCLUDE ssNoVersion] from osql, type:

osql /Usa /P <saPassword>