| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic |
|---|---|---|---|---|---|---|---|
Connect to Azure SQL Database |
Connecting to an Azure SQL Database Using SQL Server Native Client |
markingmyname |
maghan |
03/14/2017 |
sql |
native-client |
reference |
[!INCLUDE SQL Server]
Important
[!INCLUDEsnac-removed-oledb-and-odbc]
For a sample that shows how to connect to a [!INCLUDE ssazure-sqldb] using [!INCLUDEssNoVersion] Native Client, see Development: How-to Topics (Azure 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.