EXECUTE AS LOGIN is not supported - use EXECUTE AS USER instead.
Yes, but CREATE and ALTER login statements do not offer all the options (no Windows and server-level Azure Active Directory logins). Disaster recovery is discussed in Overview of business continuity with Azure SQL Database High availability is included with every database and it is not recommended to use Log-shipping as HA alternative. Natively built-in as a part of DMS migration process. Yes - Premium and Business Critical tiers only
Yes, but third-party word breakers are not supported File paths are automatically assigned and the file location cannot be specified in ALTER DATABASE ADD FILEstatement. Some - see Extended events in SQL Database See Linked server differences for cross-instance queries.īuilt-in - a single Managed Instance can have multiple databases that share the same pool of resources Yes, but only Azure Key Vault and SHARED ACCESS SIGNATURE are supported see details Yes, but only database scoped credentials. This is a defect that will be fixed soon. Yes, but without access to file system in CREATE ASSEMBLY statement - see CLR differencesĬurrently no due to defect in RESTORE including point-in-time RESTORE. Yes - Premium tier, Standard tier - S3 and above, General Purpose tier, and Business Critical tiers Yes, can be set when the instance is created and cannot be updated later. No, default logical server collation SQL_Latin1_General_CP1_CI_AS is always used. Yes, without access to file system for BACKUP and CREATE operations - see certificate differences. Yes, without access to file system for BACKUP and CREATE operations. Yes, but just from Azure Blob Storage as a source - see differences. Yes, but just from Azure Blob storage as a source. Yes - see Stored procedures, functions, triggers differences Yes, user initiated copy-only backups to Azure Blob Storage (automatic system backups cannot be initiated by user) - see Backup differences No, only system-initiated automatic backups - see Automated backups
Full backups are taken every 7 days, differential 12 hours, and log backups every 5-10 min. High availability is included with every database and cannot be managed by user. High availability is included with every database. No, see Auto-failover groups(preview) as an alternative Yes - all service tiers other than hyperscale Supported by single databases and elastic pools The following table lists the major features of SQL Server and provides information about whether the feature is partially or fully supported and a link to more information about the feature.
SQL Server feature support in Azure SQL Database Filtered to General Availability (GA) announcements for SQL Database features.Visit the Service Updates webpage for Azure for the newest updates using these filters: Microsoft continues to add features to Azure SQL Database. With Azure SQL Database, you can create a database as part of a managed instance, as a single database, or as part of an elastic pool. The features of SQL Server supported by Azure SQL Database depend on the type of Azure SQL database that you create.
Azure SQL Database shares a common code base with SQL Server.