Skip to content

connecting-to-a-windows-azure-sql-database-using-sql-server-native-client.md

Latest commit

 

History

History
31 lines (24 loc) · 2.1 KB

connecting-to-a-windows-azure-sql-database-using-sql-server-native-client.md

File metadata and controls

31 lines (24 loc) · 2.1 KB
title Native Client, connect to Azure SQL DB
ms.custom
ms.date 03/14/2017
ms.reviewer
ms.prod sql
ms.technology native-client
ms.topic reference
ms.assetid 0dc20bb6-b142-4259-b87b-427d2ba798af
author markingmyname
ms.author maghan
monikerRange >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current

Connecting to an Azure SQL Database Using SQL Server Native Client

[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]

For a sample that shows how to connect to a [!INCLUDEssSDSfull] using [!INCLUDEssNoVersion] Native Client, see Development: How-to Topics (Azure SQL Database).

Known Issues When Connecting to a SQL Database

The following are known issues when connecting to a [!INCLUDEssSDS] using [!INCLUDEssNoVersion] Native Client:

  • A connection made with SQLBrowseConnect may be rejected if SQLBrowseConnect is used in stages. For example, if the driver name is sent in the first call, server and credentials (user and password) sent in the second call, establishing the connection, and a database name and a language in the third call. The third call will cause [!INCLUDEssNoVersion] Native Client to issue a USE statement to change databases. However, the USE statement is not supported in [!INCLUDEssSDS], generating the following error:

    [Microsoft][SQL Server Native Client 11.0][SQL Server]USE statement is not supported to switch between databases. Use a new connection to connect to a different Database.

See Also

Building Applications with SQL Server Native Client