- Edited by luca93vasto Sunday, September 06, 2015 4:42 PM
- Moved by Maria AtanassovaMicrosoft contingent staff, Moderator 23 hours 5 minutes ago Reason
Here's my take on your question list.
1. Azure SQL Database is based on SQL Server. Databases are portable between Azure SQL Databases and SQL Server datatbases with the exception of a few incompatibilities (very well documented and often very explainable in the context of cloud benefits).
2. SQL Database supports local transaction but transactions spanning multiple databases (distributed transaction involving MS DTC) are not supported.
2b. With Azure SQL Database the whole point is to leave as many management feature to Azure itself while still being able to run and configure the datbase so your applications can fully leverage it can be agnostic whether the DB is a SQL Server DB or and Azure SQL Database. Things like the 'master' database, SQL users, backups and even firewall settings are configurable. Low level configuration on how data is persisted on disks f.e. is not configurable because that what Azure will handle for us.
3. You can use SQL Databases without the need to use any other Azure service. In that sense it can be regarded stand-alone. Connections to your Azure SQL Database are based on the same protocols as other db connections. To handle transient fault messages caused by service throttling client can be enhanced with retry logic.
4. Azure resources, like Azure SQL Databases, can be privisioned in multiple regions. It is a decision you make when you setup storage accounts, databases, VM's and other services.
5. The Microsoft Azure Trust Center explains the compliancy Azure offers, many of these also apply to Azure SQL Databases. In addition to that there is an SLA for Azure SQL Database that guarentees 99,99% availability (for the most recent tiers offered) .