October CTP no queries no SSMS magic

Question

uhm I cannot even query the database by connecting through new query "hack" and why if this is feature complete I cannot access the database normally in SSMS?

Answer 1

Couple of things.

The service now has a firewall.  By default, everything is disabled (wouldn't be a very effective firewall if not :)).  You have to explicitly give permission to the IP address(es) you want to use to access the service.  BTW, there is a check box 'enable all Microsoft hosted services' or something that will automatically provision for the right IP range for Windows Azure compute applications.

Make sure you configure this firewall feature properly from the new developer portal at https://sql.azure.com.  Note: there is a 5 minute timeout for the cache holding the firewall permissions in the front end of the service.  You may have to wait up to 5 minutes for changes made via the portal to take affect at the service URL. 

Second thing is that full SSMS support is part support in the SQL Azure service and part support in SSMS itself.  The service is feature complete so we're good to go there.  The full support in SSMS is due out later this fall as part of the CTP3 delivery of SQL Server Killimanjaro (next release of SQL Server).  There will be a tools-only download as part of the SQL Server CTP3 offering.  In the meantime, the previously documented workaround + the right firewall settings should get you going.  If not, please drop me a line at patricmc AT microsoft DOT com.

Hope this helps.

Patric

Answer 2

Hi Patrix,

Could you please tell me in the Ip range do we need to specify my machine IP address.

---

Thanks, Sonia

Answer 3

Hi thanks for your answer Patric about the firewall I have set the ips from 0.0.0.0 to 255.255.255.255, is this all ips? :) (since my ip is dynamic) I think this could be enhanced to get the ip based on domain (for the dynamic ip domains) but no magic still using the new query way, says database is unavailable although selectable on the database combobox, about the SSMS ok so its should be fixed by CTP3 of R2, will there be an update for R1 anytime soon to support Azure?

thanks

Answer 4

When you go to the 'firewall' tab in the new developer portal at https://sql.azure.com, you have a button and a check box.  The button will automatically add the IP address of the machine you are currently using to access the portal to the list of allowed IP addresses.  The check box will add the appropriate IP range to allow any Windows Azure compute application to access your database server.

Beyond that, you can always find out the IP address of a machine using the ping command or by visiting http://whatismyip.com/ from that machine.

Hope that helps.

Patric

Answer 5

You should be able to use the button on the fireall tab of the portal to automatically add the IP address of the current machine.  Does that work for you?

Second, the firewall settings are cached in the service front ends with an expiration time of 5 min.  So, you may have to wait up to 5 minutes before a new firewall setting takes effect at the service endpoint.

Can you give me a bit more info on what you're doing and what's failing?  Some of the connection dialogs in VS and other places (ODBC Data Source) have a few glitches yet when working against SQL Azure.  You may have run into one.  The good news is that for the vast majority of these, they are issues with the dialog code and not the connection code.  So, once you get around the dialog, you should be able to use the connection just fine.

Patric

Answer 6

When trying to query my database selecting from master to my database I get "the database ... is not accessible" about the ip address i think there is no solution yet for dynamic ips does it? and adding my current ip would not help me much because it will change at any time, so for all ips to access my database 0000 to 255255255255 does not work? by the way waiting for about an hour and no change on the error maybe im doing something wrong

Answer 7

"The database ... is not accessible" does not sound like a firewall error.  Instead, it sounds like you might have hit a service problem.

Since I see other posts of yours later on, I am assuming this got resolved.