Skip to content

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

Latest commit

 

History

History
59 lines (47 loc) · 4.29 KB

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

File metadata and controls

59 lines (47 loc) · 4.29 KB
title Run SQL Server With or Without a Network | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service database-engine
ms.service
ms.component configure-windows
ms.reviewer
ms.suite sql
ms.technology
database-engine
ms.tgt_pltfrm
ms.topic article
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
ms.assetid 54eac961-5c7a-4481-982d-f93a64b5c2f4
caps.latest.revision 26
author MikeRayMSFT
ms.author mikeray
manager craigg
ms.workload On Demand

Run SQL Server With or Without a Network

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] [!INCLUDEmsCoName] [!INCLUDEssNoVersion] can run on a network, or it can function without a network.

Running SQL Server on a Network

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

net start

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

  • Analysis Services (MSSQLSERVER)

  • SQL Server (MSSQLSERVER)

  • SQL Server Agent (MSSQLSERVER)

Running SQL Server Without a Network

When running an instance of [!INCLUDEssNoVersion] without a network, you do not need to start the built-in [!INCLUDEssNoVersion] service. Because [!INCLUDEssManStudioFull], 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 [!INCLUDEssNoVersion] are identical for a network or stand-alone operation.

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

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

osql /Usa /P <saPassword>