2 days; I'm stumped.
I created 2 Azure database servers, each with a single database.
"k7lyvky04f" was created with the classic portal. It contains a database called "asdf"
dataserver was created with the preview portal. It contains a database called "data"
I am able to migrate an on-premise database up into both servers, using SQLAzureMW v3.15.6. I was joyfully able to connect with ODBC to the master database of the "k7lyvky04f" server on the first try. I could not, however access "asdf",
which contains the migrated data.
I tried forums etc, and tried many things to try to resolve this, but now, a more serious issue has popped up, I can't connect with ODBC at all. Not even the master. I built a variety of different vms to see if the problem stemmed from the development
machine's config, but not even the most current machine will connect to either of my two databases. This leads me to believe the problem stems from the Azure side, but I made no changes there other than to allow more ip addresses in the azure-sql-configuration
tab. Also, the migration wizard *still* connects and uploads to both servers.
Here is an example ODBC and result:
Microsoft SQL Server Native Client Version 10.50.1600
Data Source Name: data on dataserver
Data Source Description: data on dataserver
Server: Adminsa@dataserver.database.windows.net
Use Integrated Security: Yes
Database: (Default)
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Server Service Principle Name(SPN):
Mirror Server Service Principle Name(SPN):
Microsoft SQL Server Native Client Version 10.50.1600
Running connectivity tests...
Attempting connection
[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [53].
[Microsoft][SQL Server Native Client 10.0]Login timeout expired
[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow
remote connections. For more information see SQL Server Books Online.
TESTS FAILED!
In Sql Server Configuration manager, Protocols for MSSQLServer TCP-IP is enabled, and Named pipes are disabled.
Any ideas?
..update: I noticed the SQL Native Client config had Named pipes enabled. I disabled it, leaving only TCP/IP and Shared Memory enabled. Now the error reads:
[Microsoft][SQL Server Native Client 10.0]TCP Provider: No such host is known.
[Microsoft][SQL Server Native Client 10.0]Login timeout expired
...