BDE Connection on Azure

Hello,
i'm having problem on connecting SQL Server Azure via BDE (Borland Database Engine),
i'm testing if we can move our DB to azure but i need to connect with BDE to SQL Azure.
BDE cannot find sql via name (like z7o15r43sm.database.windows.net). how i can connect via IP?

The default firewall for Azure Sql does not allow outside IP addresses to directly access the server. Did you add your IP address to the permitted addresses on the Portal management pages?
Paul

Similar Messages

Cannot connect to Azure Mobile Services as DataSource

I've created an Azure Mobile Service which is using .NET backend.
Project Siena isn't able to connect or work against this kind of data source.
Error message is
An error occurred connecting to Azure Mobile Service
I have also tried to create zz_config support table, and implement a custom TableController for serving the URI
tables/zz_config but I could only got few steps further, still without the possibility to read and use the model exposed by Mobile Services
This behavior has been reproduced with both Beta 2 and Beta 3
P.S. Adding the AMS as REST data source makes possible to import and use the model exposed. The operation of association in this case must be done per-table in Siena
Wheb can we expect Siena to work well together with the new version of Azure Mobile Services?
Massimo Prota
.NET MCAD - SP2007 MCTS - SP2010 MCPD and MCITP
My blog: http://blogs.ugidotnet.org/mprota - Twitter:
@massimoprota

Yes, that article is indeed precise and updated. I followed all steps described properly, especially for the part about setting up the database structure, and create
zz_config table (second post of the series)
I can connect to AMS (JS Backend) with Siena, but tables' names aren't showing up correctly, but display as
undefined, and from there on doesn't work properly.
JSON object returned from GET /tables/zz_config?$filter=(Key%20eq%20'table')
"id": "ccb9c9a8-9bae-41c8-87aa-277e2e0d1379",
"key": "table",
"value": "users"
I do confirm I have the same (incorrect) behavior using a .NET Backend where I set up
zz_config table and create a TableController mapped with it; with route
tables/zz_config
I confirm also I had the same behavior this morning with Beta 2, before I installed Beta 3.
P.S. The error message reported in my first post is returned only when the table
zz_config isn't setup correctly on AMS
Massimo Prota
.NET MCAD - SP2007 MCTS - SP2010 MCPD and MCITP
My blog: http://blogs.ugidotnet.org/mprota - Twitter:
@massimoprota

DB SCHEMA INFO error when connecting to AZURE SQL through OLE DB

Created a virtual machine in Azure and connected to Azure SQL server. I have been able to access the Azure SQL server through 2014 SQL Server Management Studio.
I have connected my program to the Azure SQL through a OLE DB connection. I am able to connect and create a new database through this connection, however when I try to connect to the newly created database, i get the following error:
Error creating connection: Not a Market(our product) database: Invalid object name 'db_schema_info'.
I am not sure what is going on and why this error is showing up. Is it because of the OLE DB connection? The fact that the login mysql.database.windows.net has periods and a login login@mysql? I have had issues with punctuation in the past when connecting
through OLE DB. Please help me to either find the right code or another work around option.
I can connect my program to a local SQL server hosted on the VM the same process as above without any issues. This is not a viable option as I need to connect multiple VMs to the same SQL server.

Hi,
Thanks for posting here.
Connecting to Microsoft Azure SQL Database by using OLE DB or ADO is not supported on SQL Azure.
Ref: http://www.connectionstrings.com/sql-azure/
Microsoft does not announce support for OLE DB connections to Azure and there are limitations. Some required OLE DB schema rowsets are not available from an Azure connection, and some properties that identify features in SQL Server are not adjusted to represent
SQL Azure limitations. For most common connect/query/update tasks it seems to work fine.
Provider=SQLNCLI11;Password=myPassword;User ID=[username]@[servername];
Initial Catalog=databasename;Data Source=tcp:[servername].database.windows.net;
Ref: http://msdn.microsoft.com/en-us/library/azure/ee336245.aspx
You can also check
Connectivity Considerations for SQL Server in Azure Virtual Machines
Hope this helps you.
Girish Prajwal

How to connect to Azure Files (preview) share?

I enabled Azure Files preview.
I follow this article: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/12/introducing-microsoft-azure-file-service.aspx
I created new storage account called loremipsum. Using powershell, I created new storage share called loremipsum-01. Called
New-AzureStorageDirectory command to test create directory. It succeeded.
I went to command prompt and called this command:
net use z: \\loremipsum.file.core.windows.net\loremipsum-01 /u:loremipsum blablablablablablamyaccesskey==
Result:
System error 64.
Network name is undefined.
How should I connect to this share, so I can use it as mapped folder in explorer?

Answer here:
http://stackoverflow.com/questions/26820246/how-to-connect-to-azure-files-preview-share :)

Azure Sql connection from azure website not working

I'm have the following connection problem when connecting to the website is deployed to azure. The site work locally when connecting to Azure Sql using the same account. The site is MVC 4 EF 5.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Here is my web.config.
<?xml version="1.0" encoding="utf-8"?>

<configuration>
<configSections>

<section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=4.4.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</configSections>
<connectionStrings>
<add name="MyWhesEntities" connectionString="metadata=res://*/MyWhesModel.csdl|res://*/MyWhesModel.ssdl|res://*/MyWhesModel.msl;provider=System.Data.SqlClient;provider connection string="data source=localhost;initial catalog=mywhes;integrated
security=True;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
<add name="MyWhesContext" connectionString="tcp:ngw4ziez6g.database.windows.net,1433;Database=mywhes;UserID=********;Password=********;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<add key="webpages:Version" value="2.0.0.0" />
<add key="webpages:Enabled" value="false" />
<add key="PreserveLoginUrl" value="true" />
<add key="ClientValidationEnabled" value="true" />
<add key="UnobtrusiveJavaScriptEnabled" value="true" />
<add key="enableSimpleMembership" value="false" />
<add key="autoFormsAuthentication" value="false" />
</appSettings>
<system.web>
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</assemblies>
</compilation>
<httpRuntime />
<machineKey />
<authentication mode="Forms">
<forms loginUrl="~/Account/Login" timeout="2880" />
</authentication>
<pages controlRenderingCompatibilityVersion="4.0">
<namespaces>
<add namespace="System.Web.Helpers" />
<add namespace="System.Web.Mvc" />
<add namespace="System.Web.Mvc.Ajax" />
<add namespace="System.Web.Mvc.Html" />
<add namespace="System.Web.Optimization" />
<add namespace="System.Web.Routing" />
<add namespace="System.Web.WebPages" />
</namespaces>
</pages>
<membership defaultProvider="WhesMembershipProvider">
<providers>
<clear />
<add name="WhesMembershipProvider" type="MyWhes.Helpers.WhesMembershipProvider" connectionStringName="MyWhesContext" />
</providers>
</membership>
<profile>
<providers>
<clear />
</providers>
</profile>
<roleManager defaultProvider="WhesRoleProvider" enabled="true" cacheRolesInCookie="true">
<providers>
<clear />
<add name="WhesRoleProvider" type="MyWhes.Helpers.WhesRoleProvider" connectionStringName="MyWhesContext" />
</providers>
</roleManager>
<sessionState mode="InProc" customProvider="DefaultSessionProvider">
<providers>
<add name="DefaultSessionProvider" type="System.Web.Providers.DefaultSessionStateProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" />
</providers>
</sessionState>
<customErrors mode="Off"></customErrors>
</system.web>
<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
</system.webServer>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
<entityFramework>
<defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
</entityFramework>
</configuration>

<connectionStrings>
<add name="MyWhesEntities" connectionString="metadata=res://*/MyWhesModel.csdl|res://*/MyWhesModel.ssdl|res://*/MyWhesModel.msl;provider=System.Data.SqlClient;provider connection string="data
source=localhost;initial catalog=mywhes;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
<add name="MyWhesContext" connectionString="tcp:ngw4ziez6g.database.windows.net,1433;Database=mywhes;UserID=********;Password=********;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" providerName="System.Data.SqlClient"
/>
</connectionStrings>
Hello James,
Your Entity Framework Model "MyWhesEntities" connection string is still pointing to a local server, not to SQL Azure; or do you change it during runtime in your code?
And you should add the "data source=" property name to your second connection string, it's missing.
Olaf Helper
* cogito ergo sum * errare humanum est * quote erat demonstrandum *
Wenn ich denke, ist das ein Fehler und das beweise ich täglich
Blog
Xing

Can't connect to Azure Website via Studio 13.1

Hello,
From the server explorer, I can connect to my Azure DB (see it visually under the Azure dropdown). But if I click 'Web Sites' it gives me a message saying I must install the sdk before I can't perform such a function. When I go to install the sdk,
it says already installed. It's just the websites feature I can't connect to azure for.
I redownloaded my publish settings, reinstalled, set up a new website, and now I have nothing. Suggestions?

Hi Adri1007,
Since this issue is related to the Azure Website, I suggest you select the correct forum here:
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/home?category=windowsazureplatform
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error connecting SQL Azure - Network access for Distributed Transaction Manager (MSDTC) has been disabled

Sometimes I have an error connecting SQL Azure. The error occurs in an asp.net application and in a windows service running on VM in Azure. Error details:
System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network
access in the security configuration for MSDTC using the Component Services Administrative tool. ---> System.Runtime.InteropServices.COMException: The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT:
0x8004D024)
   at System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction(UInt32 propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier, Guid& transactionIdentifier, OletxTransactionIsolationLevel& isolationLevel,
ITransactionShim& transactionShim)
   at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
   --- End of inner exception stack trace ---
   at System.Transactions.Oletx.OletxTransactionManager.ProxyException(COMException comException)
   at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
   at System.Transactions.TransactionStatePSPEOperation.PSPEPromote(InternalTransaction tx)
   at System.Transactions.TransactionStateDelegatedBase.EnterState(InternalTransaction tx)
   at System.Transactions.EnlistableStates.Promote(InternalTransaction tx)
   at System.Transactions.Transaction.Promote()
   at System.Transactions.TransactionInterop.ConvertToOletxTransaction(Transaction transaction)
   at System.Transactions.TransactionInterop.GetExportCookie(Transaction transaction, Byte[] whereabouts)
   at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction tx)
   at System.Data.ProviderBase.DbConnectionPool.PrepareConnection(DbConnection owningObject, DbConnectionInternal obj, Transaction transaction)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal&
connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
   --- End of inner exception stack trace ---
   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
   at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection()
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClassb.<GetResults>b__9()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
   at System.Data.Entity.Core.Objects.DataClasses.EntityReference`1.Load(MergeOption mergeOption)
   at System.Data.Entity.Core.Objects.DataClasses.RelatedEnd.DeferredLoad()
   at System.Data.Entity.Core.Objects.Internal.LazyLoadBehavior.LoadProperty[TItem](TItem propertyValue, String relationshipName, String targetRoleName, Boolean mustBeNull, Object wrapperObject)
   at System.Data.Entity.Core.Objects.Internal.LazyLoadBehavior.<>c__DisplayClass7`2.<GetInterceptorDelegate>b__2(TProxy proxy, TItem item)

Hello,
I am not an expert in MSDTC but as we know,SQL Azure Database does not support
distributed transactions. This means that SQL Azure doesn’t allow Microsoft Distributed Transaction Coordinator (MS DTC) to delegate distributed transaction handling.
One common cause of MSDTC getting involved in Entity Framework applications is the fact that we close and reopen the same connection as needed (i.e. for each query that is executed).To avoid the stack from opening and closing the connection multiple times,
you can simply open the connection explicitly and run the queries in the same connectio.
The following thread is about a similar issue, please refer to:
http://answers.flyppdevportal.com/categories/azure/sqlazure.aspx?ID=d705a8cf-cba4-494c-96f6-96a136bd29e3
What's more, you can also try the workaround that involves setting the Enlist option of the SQL Azure connection to false. For the detail explanation, please refer to:Entity
FrameWork and SQL Azure
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Can No Longer Connect to Azure SQL Databases

As of this morning, I am no longer to connect to any of my Azure SQL databases by any (apparent) means. I checked the configuration in the azure portal and my IP address is listed as an allowed IP, however:
I am unable to connect via SQL Server Management Studio
My request times out when attempting to visit https://{server_name}.database.windows.net
What might have caused this?

Hi ,
Thanks for posting here.
To resolve the issue you can try the following steps (in that order):
                Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port
(1433) and the fully qualified server name.
Note You can follow these steps to obtain the connection string from the Azure Management Portal:
                      Log on to the
Azure Management Portal.
                      In the left navigation pane, click
SQL Databases.
                      Select your Azure SQL Database server.
                      Click
Dashboard.
                      On the right side, go to the
quick glance section, and then click Show connection strings.
                Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).
                Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this,
see
Azure SQL Database connectivity troubleshooting guide and
Troubleshooting SQL Server connectivity issues.
Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.
                Try increasing the connection
timeout. Microsoft recommends using a connection timeout of at least 30 seconds.
                As a best practice ensure retry logic is in place. For more information about the retry logic, see
Azure SQL Database best practices to prevent request denials or connection termination.
              If the previous steps do not resolve your problem, follow these steps to collect more data and contact support:
                  If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing
ID.
Microsoft Customer Support Services can use this information.
                  For more information about how to enable the logging, see
how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
Azure SQL Database Development Considerations.
Please write back with the exact Error message/ Error Code if this doesn't help.
Regards,
Shirisha Paderu.

Cannot Connect to Azure SQL Database in Visual Studio 2013

Beyond Frustrated here.
I am trying to connect to an Azure SQL database - it has been created, has tables etc. I am trying to create a new Data Connection from within Visual Studio 2013, latest release for VS and Azure. I continue to receive the following error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
I have ensured that TCP is allowed and above Named Pipes in the Configuration Manager. The associated IP address is allowed on Azure Firewall. Certificate has been added to VS etc. But still no connection. I can see the database in the Azure section in Server
Explorer, but cannot add a Data Connection. What is equally as frustrating is I have a MacBook Pro running Win 7 sitting right next to my office computer and it can access Azure fine, not problems.
If anyone has any other ideas on how I might be able to solve this I would love to hear them. Thanks in advance.
Jeff

Hi,
The Error message "   A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is
configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53) "
The issue comes up mainly because the application is not able to connect to the server.
To resolve this issue, try the following steps (in that order):
Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).
2. Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port (1433) and the fully qualified server name.
Note You can follow these steps to obtain the connection string from the Azure Management Portal:
                      Log on to the
Azure Management Portal.
                      In the left navigation pane, click
SQL Databases.
                      Select your Azure SQL Database server.
                      Click
Dashboard.
                      On the right side, go to the
quick glance section, and then click Show connection strings.
Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this, see
Azure SQL Database connectivity troubleshooting guide and
Troubleshooting SQL Server connectivity issues.
Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.
Try increasing the connection timeout. Microsoft recommends using a connection timeout of at least 30 seconds.
As a best practice ensure retry logic is in place. For more information about the retry logic, see
Azure SQL Database best practices to prevent request denials or connection termination.
      If these steps do not resolve your problem, follow the below steps to collect more data and contact support:
   If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing ID.
Microsoft Customer Support Services can use this information.
   For more information about how to enable the logging, see
how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
Azure SQL Database Development Considerations.
  Check out
the list of best practices for Connecting to Windows Azure SQL Database.
Regards,
Shirisha Paderu.

Consistently getting "The wait operation timed out" when connecting to Azure SQL Database from a virtual instance...

I have a web app that is backed by a an Azure SQL Database. The problem is that I had multiple issues when connecting to the database mainly when trying to establish a connection, or timeouts. This is the log I just encountered when trying to use the web
app.
[Win32Exception (0x80004005): The wait operation timed out]
[SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21970; handshake=1; ]
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +671
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1012
System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +6712291
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +152
System.Data.SqlClient.SqlConnection.Open() +229
System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +102

Hi Affar2k,
According to your description, we need to verify if there is no network issue and the Sqlclient version is older than .NET 4.5. You can try to connect to the Windows Azure SQL database via SSMS and check if it can run well. When you
connect to the SQL Azure database via ADO.NET, you need to verify that the server name and passwords are right in the connection string.
For more information, you can review the following article about how to connect to Windows Azure SQL Database using ADO.NET.
http://msdn.microsoft.com/en-us/library/windowsazure/ee336243.aspx
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Connecting to Azure SQL database in Access 2010

I've recently purchased a new computer and I had an OBDC connection set up to link to a sql database in azure through access. I am trying to set it up on my new computer but I'm unable to define the specific database. I'm able to make the connection but
it only allows me into the master database. I've added my IP address in the configure servers but still can't get things to work. Any help would be greatly appreciated.
thanks
Lynn

Hi,
The following guidelines apply to SQL Database connections using ODBC:
• When using SQL Server Native Client from SQL Server 2008 R2 or SQL Server 2008, the connection string must include the server name as part of the user name (user@server).
• You must use TCP/IP as the protocol when connecting to an Azure SQL Database.
• You cannot create a table in the master database, so therefore you must create a user database to create a table.
• You cannot execute a use database command to switch to your user database. You must disconnect and connect directly to the user database.
• You must have a primary key or clustered index on your table to be able to insert data.
Ref:
https://msdn.microsoft.com/en-us/library/azure/hh974312.aspx?f=255&MSPPError=-2147217396
http://blogs.office.com/2010/06/07/access-2010-and-sql-azure/
https://support.microsoft.com/en-us/kb/2028911/
Hope this helps you.
Girish Prajwal

How to connect to Azure SQL database remotely (SharePoint 2013 BI)

Hi,
I am new to using Azure VM's and I am looking for advice. I have created and can connect to an Azure VM with a SQL Server 2012 installed on it (includes SSAS and SSRS). I connect to the VM using Microsoft Remote Desktop Connection.
The problem I am having is connecting to the Azure database from a SharePoint BI site. Are there any good videos or websites that demonstrate how to setup an Azure VM so a user can access a database remotely.
I hope you can help.
ATaylor

Hello,
To connect to the SQL Server Database from another computer, you must know the Domain Name System (DNS) name of the Azure virtual machine. For example: DNSName,portnumber such as SQLVM.cloudapp.net,57500.
(Note: The port number is the public endpoint port which you can configure in the management portal for TCP communication with SQL Server on Azure VM.)
As for datasource credentials, you can use a SQL Server authentication login: create a SQL Server login with password on the SQL Server instance.
Reference:
Complete Configuration steps to connect to the virtual machine Using SQL Server Management Studio on another computer
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Connect to Azure SQL DB with Security Enabled Access required using SSMS

I'm looking to connect to an Azure SQL DB with Security Enabled Access required using SQL Server Management Studio 2014. I have tried checking off "Encrypt connection", but still errors out with "Cannot open database 'db name' on server 'hostname'
requested by the login. Access to the database is only allowed using a security-enabled connection string."
Thanks,
Scott

Hi Scott,
Sorry, I missunderstood your initial question and the documentation I referenced is not updated appropriately. You have to change the connection string to <server-name>.database.secure.windows.net when you enable the security/auditing features.
Documentation for this can be found
here
Thanks,
Jan

Connect to Azure Sql DB through WCF Data Service

I am following the tutorial:
http://msdn.microsoft.com/en-us/library/windowsazure/ee621789.aspx;
Connect to Windows Azure SQL Database Through WCF Data service on a
Windows 8 machine running VS2013. Until starting this tutorial, I have only been using VS for WPF applications. So it might not be properly configured for a web app.
Everything works just fine until I get to the section on Creating the Client Application. Clicking the Discover button populates the services pane with my service. When I click on the service in the pane I get the following Add Service Reference
Error:
There was an error downloading 'http://localhost:62778/testDataService.svc/_vti_bin/ListData.svc/$metadata'.
The request failed with the error message: --- , . . .
If I ignore it and click OK it essentially tells me the same thing:
"There was an error downloading metadata from the address. Please verify that you have entered a valid address."
I am thinking that there is a configuration issue on my machine. Perhaps something needs to be installed or running, . . .
I have tried doing the same steps with a local SqlExpress database, and get the same problem. If I try to go directly to the website via the browser:
http://localhost:62778/testDataService.svc
I get a Request Error.
Any suggestions, thoughts on this will be greatly appreciated!
Robotuner

Hi,
From the error message "There was an error downloading 'http://localhost:62778/testDataService.svc/_vti_bin/ListData.svc/$metadata'.", I suspect that you created a folder named _vti_bin, and created wcf data service named ListData, in my test
application, from my experience, you issue may be caused by "$metadata", can you give further information to me, there was a
wcf data service quick start, hope this will help you.
Best Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Managing connection strings Azure Cloud service deployment

I have an azure cloud service project which comprises of one worker role and one web role. I need to have both staging and live deployments but I need them to have different connection strings because the worker role generates lots of data which is reported
by the web application and I would not want to have test data in production.
What's the best way to configure this so that I can quickly swap or promote from staging to live and have the connection strings just update without having to republish from visual studio using a different configuration.

Hi,
Two ways to do it -
1. Keep your connection strings in cscfg so that you can change those on the fly after the deployment using azure management portal.
2. Keep connection string in the web configuration file at the time of deployment and have cscfg settings which can override those i.e. re-write those in the web configuration file when role instances are restarted.
I too experienced something similar to this but not for connection strings, it was for ACS i.e. authentication settings which I needed to have differently on both deployment slots, refer my blog post http://passionatetechie.blogspot.in/2014/02/moving-acs-settings-in-cloud.html you
can do similar for connection strings of your application.
Bhushan | < href='http://www.passionatetechie.blogspot.com'>Blog | <a href="http://in.linkedin.com/pub/bhushan-gawale/29/327/405"> LinkedIn</a> | <a href="http://twitter.com/BhushanGawale">Twitter</a>

BDE Connection on Azure

Similar Messages

Maybe you are looking for