You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|Microsoft.Network/loadBalancers (only for Standard SKUs)| Yes|[Load Balancers](../../azure-monitor/platform/metrics-supported.md#microsoftnetworkloadbalancers)|
51
54
|Microsoft.Network/publicipaddresses | N/A |[Public IP Addresses](../../azure-monitor/platform/metrics-supported.md#microsoftnetworkpublicipaddresses)|
Copy file name to clipboardExpand all lines: articles/sql-database/sql-database-managed-instance-get-started-restore.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,12 +29,12 @@ This quickstart:
29
29
- Uses resources from the [Create a Managed Instance](sql-database-managed-instance-get-started.md) quickstart.
30
30
- Requires your computer have the latest [SQL Server Management Studio](https://docs.microsoft.com/sql/ssms/sql-server-management-studio-ssms) installed.
31
31
- Requires using SSMS to connect to your Managed Instance. See these quickstarts on how to connect:
32
+
-[Enable public endpoint](sql-database-managed-instance-public-endpoint-configure.md) on Managed Instance - this is recommended approach for this tutorial.
32
33
-[Connect to an Azure SQL Database Managed Instance from an Azure VM](sql-database-managed-instance-configure-vm.md)
33
34
-[Configure a point-to-site connection to an Azure SQL Database Managed Instance from on-premises](sql-database-managed-instance-configure-p2s.md).
34
-
- Requires Azure Blob Storage Account (for example Standard_LRS V2) on **public IP** protected with **SAS credential** that has `rw` permission. [Private IPs for blob storage protected by firewall](https://docs.microsoft.com/azure/storage/common/storage-network-security) and Azure Blob Storage service endpoints are currently not supported.
35
35
36
36
> [!NOTE]
37
-
> For more information on backing up and restoring a SQL Server database using Azure Blob storage and a [Shared Access Signature (SAS) key](https://docs.microsoft.com/azure/storage/common/storage-dotnet-shared-access-signature-part-1), see [SQL Server Backup to URL](https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/sql-server-backup-to-url?view=sql-server-2017).
37
+
> For more information on backing up and restoring a SQL Server database using Azure Blob storage and a [Shared Access Signature (SAS) key](https://docs.microsoft.com/azure/storage/common/storage-dotnet-shared-access-signature-part-1), see [SQL Server Backup to URL](https://docs.microsoft.com/sql/relational-databases/backup-restore/sql-server-backup-to-url?view=sql-server-2017).
38
38
39
39
## Restore the database from a backup file
40
40
@@ -80,7 +80,11 @@ In SSMS, follow these steps to restore the Wide World Importers database to your
7. When the restore completes, view it in Object Explorer.
83
+
7. When the restore completes, view the database in Object Explorer. You can verify that database restore is completed using [sys.dm_operation_status](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-operation-status-azure-sql-database) view.
84
+
85
+
> [!NOTE]
86
+
> Database restore operation is asynchronous and retriable. You might get some error is SQL Server Management Studio if connection breaks or some time-out expires. Azure SQL Database will keep trying to restore database in the background, and you can track the progress of restore using the [sys.dm_exec_requests](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-requests-transact-sql) and [sys.dm_operation_status](https://docs.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-operation-status-azure-sql-database) views.
87
+
> In some phases of restore process you will see unique identifier instead of actual database name in the system views. Learn about `RESTORE` statement behavior differences [here](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-transact-sql-information#restore-statement).
Copy file name to clipboardExpand all lines: articles/sql-database/tutorial-managed-instance-azure-active-directory-migration.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.topic: tutorial
8
8
author: GitHubMirek
9
9
ms.author: mireks
10
10
ms.reviewer: vanto
11
-
ms.date: 10/22/2019
11
+
ms.date: 10/30/2019
12
12
---
13
13
14
14
# Tutorial: Migrate SQL Server on-premises Windows users and groups to Azure SQL Database managed instance using T-SQL DDL syntax
@@ -36,6 +36,8 @@ To complete this tutorial, the following prerequisites apply:
36
36
- Access to Active Directory to create users/groups.
37
37
- An existing SQL Server in your on-premises environment.
38
38
- An existing managed instance. See [Quickstart: Create an Azure SQL Database managed instance](sql-database-managed-instance-get-started.md).
39
+
- A `sysadmin` in the managed instance must be used to create Azure AD logins.
40
+
-[Create an Azure AD admin for managed instance](sql-database-aad-authentication-configure.md#provision-an-azure-active-directory-administrator-for-your-managed-instance).
39
41
- You can connect to your managed instance within your network. See the following articles for additional information:
40
42
-[Connect your application to Azure SQL Database managed instance](sql-database-managed-instance-connect-app.md)
41
43
-[Quickstart: Configure a point-to-site connection to an Azure SQL Database Managed Instance from on-premises](sql-database-managed-instance-configure-p2s.md)
@@ -209,7 +211,7 @@ Follow our [Quickstart: Restore a database to a managed instance](sql-database-m
209
211
210
212
Execute the ALTER USER command to complete the migration process on managed instance.
211
213
212
-
1. Sign into your managed instance using the SQL Admin account for managed instance. Then create your Azure AD login in the managed instance using the following syntax:
214
+
1. Sign into your managed instance using the SQL Admin account for managed instance. Then create your Azure AD login in the managed instance using the following syntax. For more information, see [Tutorial: Managed instance security in Azure SQL Database using Azure AD server principals (logins)](sql-database-managed-instance-aad-security-tutorial.md).
0 commit comments