Azure SQL service in Germany - azure-sql-database

Although Azure seems to have datacenters in Germany, I cannot select that region when creating a new SQL server on Azure Portal.
The Azure pricing page show prices for this region, so why it is not listed in the available options? Any restrictions?

There are restrictions on some Azure regions, based on your Azure account. A US based Azure account will typically not be able to use these regions for tax and legal reasons.
Full details on the German data-center GA is at this blog https://azure.microsoft.com/en-us/blog/microsoft-azure-germany-now-available-via-first-of-its-kind-cloud-for-europe/
Customers in the EU and EFTA can continue to use Microsoft cloud options as they do today, or, for those who want the option, they’re able to use the services from German datacenters

Since 2016 unfortunately nothing has changed until now (2023). Region Germany West Central (Frankfurt/Main) is available for Azure SQL but you can't create one. I worked last year a few month to install our infrastructure at Azure in that region until trying to create Azure SQL. You will get an error message when selecting the server location: "This location is not available". This has nothing to do with free or pay-as-you-go subscription. The answer from the dev support after opening a ticket (october 2022):
"Unfortunately, due to high demand for Azure SQL in this region, we
are not able to approve your quota request at this time. To ensure
that all customers can access the services they need, we are working
through approving quota requests as we bring additional capacity
online. We are continually investing in additional infrastructure to
expand our available resources. Apologies for the delay in being able
to increase the quota on your Azure subscription. No additional
details are needed from you at this time, your request will stay
pending. Thank you for your patience until we report back."
The problem is that microsoft is not working transparent und you loose so much time and money. They simply have no resources anymore.
People are asking this but they don't get answers and their questions get locked:
https://social.technet.microsoft.com/forums/en-US/94278a11-c5ac-4239-b092-a256bb5c4488/why-germany-west-central-location-is-not-available-for-subscription?forum=ssdsgetstarted
https://social.msdn.microsoft.com/Forums/en-US/ac0376cb-2a0e-4dc2-a52c-d986989e6801/unable-to-create-sql-database-server?forum=ssdsgetstarted#00a598f2-5fd4-4c7e-ab91-913fae5ba7cc
https://github.com/MicrosoftDocs/azure-docs/issues/52606
I am wondering whether Azure SQL resources in this region will be available after some time or not?

Related

Azure region not listed in some subscriptions when creating new Azure SQL server

We have a handful of Azure subscriptions through the Bizspark program. Some of our subscriptions allow creating new Azure SQL Servers in the "US West" region but others do not.
The Azure status page does not show any availability issues. The closest I found to an answer was this post from mid-December where the last answer hints that there may be region restrictions when a subscription is linked to an MSDN benefit.
Can anyone confirm the above restriction? If so, why would it impact some subscriptions and not others if they were all created via Bizspark? Is this a new restriction so older subscriptions were not affected? Is there any way to have the restriction removed?

Can't create Azure SQL Database in Australia

I am trying to create a Azure SQL Database located in Australia Southeast. The problem is when I go to create a new server the Australian location (and others ) are missing from the location drop down.
Here is what I see on the Azure portal. I can create other resources (Web app) in Australia without a problem.
Any help would be great
Some subscriptions have restrictions on creating Compute and SQL resources in certain regions. The behavior you noticed was expected due to the subscription type and is not a service degradation. We are working on better communicating such region restriction information to make it clearer. We apologize for any confusion this might have caused.
Disclaimer: I am a Program Manager for Microsoft, working on SQL Server
Please have a look here. Even the Azure Management portal has both the Australian locations.

Best Approach for syncing Azure SQL Database

Right now, our application only has one Web Site instance along with SQL Database deployed at Azure US datacenter. We are looking for deploying more Web Site instance at other datacenter such as APAC and Europe. There still be a local SQL Database for each of those web site instance. We would like end user could fail over to another instance if his registered instance is not available, such as if US web site instance is down, we could fail over user to Europe instance. With this, we would need to synchronize local SQL Database at all data centers, US, Europe and APAC.
So we are looking for what's best approach to implement the database synchronization here for Azure SQL Database. Here are what we found at this point:
Azure Data Sync, it looks like that it is the perfect choice since it is available right away at Azure Management Portal and it would be up and running with some simple configuration. However there seems couple catches. The feature has been on preview about 2 years now (see this link with the following quote from comment):
SQL Data Sync has been in preview for over 2 years and the last update was December 2012. Has this been abandoned? Is this a technology we should encourage our clients to use? There absolutely needs to be an ability to synchronize data between a local SQL DB and Azure but Microsoft seems to have dropped this and I'm leery of putting a client on this only to find that the plug has been pulled. You owe it to your users to give us some information
I also saw the post Azure data sync not syncing all databases at SO, it seems that this feature is a second class feature at Azure and MS doesn't really pay sufficient attention to it. So I am worried how good it is.
Microsoft Sync Framework, it seems a more generic sync framework and more suitable for client and server sync instead of sync among server database. Plus it is not simple as above SQL Data Sync which is available just by configuration at Azure.
Any other suggestions on sql database sync at Azure? It would be really appreciated if you could share your experience here.
Thanks very much in advance for your insight.
Update:
Azure Data Sync is built upon using Microsoft Sync Framework: see link, the quote:
Microsoft SQL Data Sync is a cloud-based data synchronization service built on the Microsoft Sync Framework technologies.
Since no one is answering this question and I am going to do it myself. Based on some latest information, the Azure Data Sync is buggy and can not be used for production at this point. I guess that's the reason why it never moves out of preview even after around 2 years. There is no other good approach for handling Azure SQL Database sync at this point unless you want to build something yourself.
you can use RedGate Data Compare to sync your Azuresql DB with your Local DB

Need to try out bigquery and google cloud sql free package, am asked to enable billing before creating an instance

Members, I have been trying to learn how to use google bigquery and the cloud sql though I have had a challenge with enabling billing issues, this is all because I needed is to have a free access package.
Question:
Is there a free package to enable me practice google cloud sql and bigquey, if yes please get me the link.
Besides any one experiencing the same problem?
This topic is not a programming question, so I will close it.
FYI:
BigQuery offers a free query tier for all users (the first 100 GB of data processed per month is at no charge). If you plan on using your own data, and not just test BigQuery with our sample public datasets, then you must enable billing, as there is no free storage tier. See: https://developers.google.com/bigquery/pricing
The D0 tier of Cloud SQL is less than a dollar a day, see:
https://developers.google.com/cloud-sql/docs/billing

SQL Azure privacy issues

I only starting to learn about SQL Azure, have spoken to some potential clients, they say they have not chosen Azure due to the private nature of their customers information.
Reading about Azure it has firewalls to prevent unauthorised access.
I was just wonder what other way I could market Azure so that clients who potentially want to use it would not be concerned about privacy issues.
Also as I understand Azure supports Hybrid solutions where you can store data locally or remotely?
Thanks
SQL Azure is a public service and the data is stored somewhere in the cloud provider facility. With all security measures including firewalls and sentry dogs the data is still under zero customer control.
So the provider could do some backup and store it for some very long time and you might want to destroy the data ASAP and will be unable to have it done.
Also here's what technically could happen (not that I'm saying it is likely):
the provider might dispose of undestroyed hard disks
a bug could cause the authorization to fail and allow an unauthenticated user (because you see, you don't control what software updates the provider applies)
the provider employee might be bribed and copy the data
So if the user really wants privacy (or the laws say the data he deals with must be processed according to certain requirements) or he wants actual control on how the data is dealt with then a public storage service like SQL Azure is technically inapplicable for him. You trying to market Azure as providing the same level of control and security as a local facility would provide are deceiving the customer.
Sad but true and you can't lie to the compiler. There's no such thing as control over your data in a public storage service. Risks of negative outcomes are perceived as rather low, but they exist and they are real.
Yes, the Azure service bus has connecting private and public clouds as a feature. Keeping sensitive data locally may be what your clients want/need to push parts of their infrastructure to the cloud, although it will take some effort for sure to keep that separation clear, and I'm not just talking technically.
That said, marketing Azure to a client that's not ready for the cloud may very well lose you the entire deal, so make sure you're not pushing anything they aren't ready to cope with to start with.
A good starting point is the Windows Azure Trust Center to learn about Windows Azure privacy and security.
There's also a 7-part Windows Azure security best practice series on the ISV Developer Community Blog. Part 1 has links to the remaining entries, at the end of the post.
Microsoft's data centers are run by Global Foundation Services, which has its own set of security and compliance. There you'll find a data center tour video