August 7, 2013 at 7:02 am
Hello,
I have just started out on SQL Azure, and I am finding that when I try to connect to SQL Azure, I have to keep running SP_Set_Firewall to allow my IP address, or add a range. Now, what I am curious about is whether there is another way to connect without doing either of these?
For example, if a company is running an application and had people working globally getting different IP Address' on a daily basis, they would just be connecting, they would not need to have their IP address allowed access all the time, so how is this done?
Thanks in advance for any help on this.
Regards,
Paul.
August 14, 2013 at 4:55 am
Usually you'll be looking at one of two scenarios. You're going to be accessing the WASD database from a web page, also residing in Azure. There you don't have to sweat the firewall rules all the time, so you'll only have to worry about it for administrative connections. Or, you have fixed IP address for particular machines that will be connecting to the WASD database.
If neither of these is true, you have choices, keep assigning connectivity on an ad hoc basis, assign a range if possible IP addresses from your IP stack, assign the entire possible IP address range.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 15, 2013 at 4:11 am
Hi Grant,
Thanks for the reply, most appreciated. I get the feeling that there are a few shortcoming in SQL Database, however, as its changing every few months, I believe that it could start getting a lot more popular. I think that security and a lack of traditional backups may be factor in keeping people off SQL Database at the moment. If MS finds a way of encrypting the data stored (rather than having to design an application to do it), and then address backup issues, the uptake would be higher.
What do you think? Are you using the cloud at the moment?
Regards,
D.
August 15, 2013 at 4:50 am
Yeah, my company is using it for several projects right now. It's working for what we need. If your needs are very traditional, then WASD isn't for you. I do hope they get the security to be a little better than SQL logins.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 22, 2014 at 4:30 am
Grant
How can the WASD Firewall be configured to allow Azure Weblications? They are internal to Azure with no external IP?
April 22, 2014 at 4:42 am
SQL Swerver (4/22/2014)
GrantHow can the WASD Firewall be configured to allow Azure Weblications? They are internal to Azure with no external IP?
All the cloud services that I currently have (not that many), have a public virtual ip address issued by the DNS within the virtual network.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply