Any additional feedback? Skip Submit. Submit and view feedback for This product This page. View all page feedback. Supports most on-premises database-level capabilities.
The most commonly used SQL Server features are available. Built-in backups, patching, recovery. Latest stable Database Engine version. Built-in advanced intelligence and security. Supports almost all on-premises instance-level and database-level capabilities. High compatibility with SQL Server. Easy migration from SQL Server. You have full control over the SQL Server engine.
Supports all on-premises capabilities. Up to Full parity with the matching version of on-premises SQL Server. Fixed, well-known Database Engine version.
You have the ability to deploy application or services on the host where SQL Server is placed. Migration from SQL Server might be challenging. Some SQL Server features are not available. No guaranteed exact maintenance time but nearly transparent. Compatibility with the SQL Server version can be achieved only using database compatibility levels. There is still some minimal number of SQL Server features that are not available. You need to manage your backups and patches.
You need to implement your own High-Availability solution. The instance can support as many databases as needed. With SQL virtual machines, you can have applications that run partly in the cloud and partly on-premises.
For example, you can extend your on-premises network and Active Directory Domain to the cloud via Azure Virtual Network. See Restore differences. Restore database from backup. From automated backups only - see SQL Database recovery. Restore database to SQL Server. Semantic search. Service Broker. Yes, but only within the instance. See Service Broker differences. Server configuration settings. Set statements. SQL Server Agent. No - see Elastic jobs preview.
SQL Server Auditing. Yes - see Auditing differences. System stored functions. System stored procedures. System tables. System catalog views. Temporary tables. Trace flags. Yes, but only limited set of global trace flags. See DBCC differences. Transactional Replication. Yes, Transactional and snapshot replication subscriber only. Yes, in public preview. See the constraints here. Transparent data encryption TDE. Windows Server Failover Clustering. Other techniques that provide high availability are included with every database.
Active geo-replication. No, see Auto-failover groups as an alternative. Yes, see Auto-failover groups. Yes, but only in serverless model. In the non-serverless model, the change of service tier change of vCore, storage, or DTU is fast and online. The service tier change requires minimal or no downtime. No, you need to choose reserved compute and storage.
The change of service tier vCore or max storage is online and requires minimal or no downtime. Full backups are taken every 7 days, differential 12 hours, and log backups every min. Automatic tuning indexes. Availability Zones. Azure Resource Health. Yes - see Elastic jobs preview. No SQL Agent can be used instead. Long-term backup retention - LTR. Policy-based management. Needs to be explicitly enabled and port must be enabled in NSG rules.
Public IP can be disabled if needed. See Public endpoint for more details. Point in time database restore. By default, Gen5, 2 vCores, 32 GB storage configuration will be offered. Through the Configure database option, we can choose other purchasing model. This is the most important option during creating a database because we determine the performance of the database on this screen. For the vCore-based purchasing model, we can change the number of vCores so that we can increase or decrease the performance of the database.
In addition, we can find out the cost summary of the selected purchasing model according to the Azure account location currency. After clicking the Create button, the Azure SQL Database has been starting to deploy and the status of the deployment process will be shown under the Notifications menu.
Once the deployment is done, the notification will be changed to Deployment succeeded and when we click this link, we can show the Deployment Details. After creating the database on Azure, we can connect and use it. We will write the name of the deployed database in the search textbox and the deployed database will appear. In this screen, we can monitor and manage the database. Also, we can configure the features and settings of the firewall.
In this query editor, we can perform the DML statements and we can also expand the tables, views and stored procedures in the database. In order to connect to a database out of the Azure Portal, we need to configure the firewall settings of the server. We will click the Set server firewall button. In the Firewall settings screen, we will click the Add client IP and it automatically finds the public IP and adds a new rule to the list. Finally, we will click the Save option to configure this setting.
The Object Explorer tab will be shown on the connected server and the databases which are placed under this server.
0コメント