Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://learn.microsoft.com/en-us/sql/sql-server/connect-to-database-engine below:

Connect to the SQL Server Database Engine - SQL Server

This article provides a high level overview for connecting to the SQL Server Database Engine, used by the following products and services:

• SQL Server
• Azure SQL Database
• Azure SQL Managed Instance
• Analytics Platform System (PDW)
• Azure Synapse Analytics

You connect to the Database Engine using a client tool or client library. Client tools run in a graphical user interface (GUI), or a command-line interface (CLI).

The following table describes some of the more common client tools.

When you connect to the Database Engine, you must provide an instance name (that is, the server or instance where the Database Engine is installed), a network protocol, and a connection port, in the following format:

[<protocol>:]<instance>[,<port>]

The protocol and port are optional because they have default values. Depending on the client tool and client library, they can be skipped.

Note

If you use a custom TCP port for connecting to the Database Engine, you must separate it with a comma (,), because the colon (:) is used to specify the protocol.

tcp is the default when connecting to Azure SQL services.

For more information, see Network protocol considerations in the next section.

If you're connecting to a named instance, you must specify the server name and the instance name, separated by a slash. For example, MyServer\MyInstance. A named instance on the local machine is specified by .\MyInstance. SQL Server Express uses MyServer\SQLEXPRESS.

SQL Server on Windows, including SQL Server Express edition, can be configured as a named instance and might also have a custom port.

For connecting to Azure SQL services, see the Connect to Azure SQL section.

For more information about custom ports with SQL Server, see SQL Server Configuration Manager.

For SQL Server on Windows, when you connect to an instance on the same machine as the client tool, and depending on which edition is installed, the default protocol can be configured with multiple protocols, including named pipes (np), TCP/IP (tcp), and shared memory (lpc). Use the shared memory protocol for troubleshooting when you suspect the other protocols are configured incorrectly.

If you connect to SQL Server over a TCP/IP network, make sure that TCP/IP is enabled on the server as well. TCP/IP might be disabled by default on installations of SQL Server. For more information, see Default SQL Server Network Protocol Configuration.

Connections to Azure SQL services, SQL Server on Linux, and SQL Server in containers, all use TCP/IP.

For both Azure SQL Database and Azure SQL Managed Instance, see Azure SQL Database and Azure SQL Managed Instance connect and query articles.

This section provides information on connecting to Azure SQL services.

This section provides information on connecting to SQL Server.

You can connect to the local machine using named pipes (np), shared memory (lpc), or TCP/IP (tcp). Shared memory is the fastest, because it doesn't use the network interface.

Note

If you use an IP address for your instance name and don't specify tcp, the protocol defaults to np (named pipes) if it's a configured protocol.

A named instance has a dynamically assigned TCP port. If you want to connect to a named instance, the SQL Server Browser service must be running on the server.

1. If you're connecting to a server configured with default settings, use one of the following options:

   • localhost
   • 127.0.0.1
   • . (a single period)

2. If you're connecting to a custom TCP port, such as 51433, use one of the following options:

   • tcp:localhost,51433
   • 127.0.0.1,1433

In this example, the named instance is called MyInstance. Make sure the SQL Server Browser service is running, and use one of the following options:

• localhost\MyInstance
• 127.0.0.1\MyInstance
• .\MyInstance

You can connect using a server name or an IP address. In this example, the server name MyServer resolves to 192.10.1.128.

To connect to a server on the local network with named pipes, use one of the following options:

• MyServer
• np:MyServer

Note

On a local area network, connecting with TCP/IP might be faster than with named pipes.

1. If you're connecting to a server configured with default TCP port 1433, use one of the following options:

   • tcp:MyServer
   • tcp:192.10.1.128

2. If you're connecting to a server configured with a custom TCP port, such as 51433, use one of the following options:

   • MyServer,51433
   • tcp:MyServer,51433
   • 192.10.1.128,51433
   • tcp:192.10.1.128,51433

In this example, the named instance is called MyInstance. Make sure the SQL Server Browser service is running on the server, and use one of the following options:

• tcp:MyServer\MyInstance
• tcp:192.10.1.128\MyInstance

Once you connect successfully to the Database Engine using a client tool, you can execute a Transact-SQL (T-SQL) query or script.

Tip

In SQL Server Management Studio and Visual Studio Code, paste or type the query into a new query window.

For more information about running T-SQL queries in client tools, see:

• SQL Server Management Studio (SSMS)
• Quickstart: Connect to and query a database with the MSSQL extension for Visual Studio Code
• sqlcmd utility
• Azure portal query editor for Azure SQL Database
• Query with the SQL query editor

Note

Some tools require a batch separator to know that a query is ready to be executed. For example, you might need to put the GO separator at the end of a T-SQL query in sqlcmd to make sure that the T-SQL query runs.

• Create a valid connection string using the shared memory protocol
• Create a valid connection string using TCP/IP
• Troubleshoot connectivity issues in SQL Server
• Trace the network authentication process to the Database Engine

• Sign in to SQL Server
• What is SQL Server Management Studio (SSMS)?
• What is the MSSQL extension for Visual Studio Code?
• Configure Database Engine Instances (SQL Server)
• sqlcmd utility

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4