Skip to content

Commit 3cca8a4

Browse files
MashaMSFTMashaMSFT
committed
fixing known issues, and images
1 parent 700305f commit 3cca8a4

File tree

3 files changed

+58
-58
lines changed

3 files changed

+58
-58
lines changed

‎articles/azure-sql/database/media/purchasing-models/pricing-model.png

-17.8 KB
Loading

‎articles/azure-sql/managed-instance/doc-changes-updates-known-issues.md

Lines changed: 40 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -25,10 +25,10 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
2525
|[Misleading error message on Azure portal suggesting recreation of the Service Principal](#misleading-error-message-on-azure-portal-suggesting-recreation-of-the-service-principal)|Sep 2021|||
2626
|[Changing the connection type does not affect connections through the failover group endpoint](#changing-the-connection-type-does-not-affect-connections-through-the-failover-group-endpoint)|Jan 2021|Has Workaround||
2727
|[Procedure sp_send_dbmail may transiently fail when @query parameter is used](#procedure-sp_send_dbmail-may-transiently-fail-when--parameter-is-used)|Jan 2021|Has Workaround||
28-
|[Distributed transactions can be executed after removing Managed Instance from Server Trust Group](#distributed-transactions-can-be-executed-after-removing-managed-instance-from-server-trust-group)|Oct 2020|Has Workaround||
29-
|[Distributed transactions cannot be executed after Managed Instance scaling operation](#distributed-transactions-cannot-be-executed-after-managed-instance-scaling-operation)|Oct 2020|Has Workaround||
28+
|[Distributed transactions can be executed after removing managed instance from Server Trust Group](#distributed-transactions-can-be-executed-after-removing-managed-instance-from-server-trust-group)|Oct 2020|Has Workaround||
29+
|[Distributed transactions cannot be executed after managed instance scaling operation](#distributed-transactions-cannot-be-executed-after-managed-instance-scaling-operation)|Oct 2020|Has Workaround||
3030
|[Cannot create SQL Managed Instance with the same name as logical server previously deleted](#cannot-create-sql-managed-instance-with-the-same-name-as-logical-server-previously-deleted)|Aug 2020|Has Workaround||
31-
|[BULK INSERT](/sql/t-sql/statements/bulk-insert-transact-sql)/[OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql) in Azure SQL and `BACKUP`/`RESTORE` statement in Managed Instance cannot use Azure AD Manage Identity to authenticate to Azure storage|Sep 2020|Has Workaround||
31+
|[BULK INSERT](/sql/t-sql/statements/bulk-insert-transact-sql)/[OPENROWSET](/sql/t-sql/functions/openrowset-transact-sql) in Azure SQL and `BACKUP`/`RESTORE` statement in SQL Managed Instance cannot use Azure AD Manage Identity to authenticate to Azure storage|Sep 2020|Has Workaround||
3232
|[Service Principal cannot access Azure AD and AKV](#service-principal-cannot-access-azure-ad-and-akv)|Aug 2020|Has Workaround||
3333
|[Restoring manual backup without CHECKSUM might fail](#restoring-manual-backup-without-checksum-might-fail)|May 2020|Resolved|June 2020|
3434
|[Agent becomes unresponsive upon modifying, disabling, or enabling existing jobs](#agent-becomes-unresponsive-upon-modifying-disabling-or-enabling-existing-jobs)|May 2020|Resolved|June 2020|
@@ -116,22 +116,22 @@ BEGIN
116116
END
117117
```
118118

119-
### Distributed transactions can be executed after removing Managed Instance from Server Trust Group
119+
### Distributed transactions can be executed after removing managed instance from Server Trust Group
120120

121-
[Server Trust Groups](../managed-instance/server-trust-group-overview.md) are used to establish trust between Managed Instances that is prerequisite for executing [distributed transactions](../database/elastic-transactions-overview.md). After removing Managed Instance from Server Trust Group or deleting the group, you still might be able to execute distributed transactions. There is a workaround you can apply to be sure that distributed transactions are disabled and that is [user-initiated manual failover](../managed-instance/user-initiated-failover.md) on Managed Instance.
121+
[Server Trust Groups](../managed-instance/server-trust-group-overview.md) are used to establish trust between managed instances that is prerequisite for executing [distributed transactions](../database/elastic-transactions-overview.md). After removing managed instance from Server Trust Group or deleting the group, you still might be able to execute distributed transactions. There is a workaround you can apply to be sure that distributed transactions are disabled and that is [user-initiated manual failover](../managed-instance/user-initiated-failover.md) on managed instance.
122122

123-
### Distributed transactions cannot be executed after Managed Instance scaling operation
123+
### Distributed transactions cannot be executed after managed instance scaling operation
124124

125-
Managed Instance scaling operations that include changing service tier or number of vCores will reset Server Trust Group settings on the backend and disable running [distributed transactions](../database/elastic-transactions-overview.md). As a workaround, delete and create new [Server Trust Group](../managed-instance/server-trust-group-overview.md) on Azure portal.
125+
SQL Managed Instance scaling operations that include changing service tier or number of vCores will reset Server Trust Group settings on the backend and disable running [distributed transactions](../database/elastic-transactions-overview.md). As a workaround, delete and create new [Server Trust Group](../managed-instance/server-trust-group-overview.md) on Azure portal.
126126

127127
### Cannot create SQL Managed Instance with the same name as logical server previously deleted
128128

129-
After [logical server](../database/logical-servers.md) is deleted, there is a threshold period of 7 days before the name is released from the records. In that period, SQL Managed Instance with the same name cannot be created. As a workaround you would need to use different name for the SQL Managed Instance or create a support ticket for releasing a logical server name.
130-
After [logical server](./logical-servers.md) is deleted, there is a threshold period of 7 days before the name is released from the records. In that period, SQL Managed Instance with the same name cannot be created. As a workaround you would need to use different name for the SQL Managed Instance or create a support ticket for releasing a logical server name.
129+
A DNS record of `<name>.database.windows.com` is created when you create a [logical server in Azure](../database/logical-servers.md) for Azure SQL Database, and when you create a SQL Managed Instance. The DNS record must be unique. As such, if you create a logical server for SQL Database and then delete it, there is a threshold period of 7 days before the name is released from the records. In that period, a SQL Managed Instance cannot be created with the same name as the deleted logical server. As a workaround, use a different name for the SQL Managed Instance, or create a support ticket to release the logical server name.
130+
131131

132132
### BULK INSERT and BACKUP/RESTORE statements should use SAS Key to access Azure storage
133133

134-
Currently, it is not supported to use `DATABASE SCOPED CREDENTIAL` syntax with Managed Identity to authenticate to Azure storage. Microsoft recommends using a [shared access signature](../../storage/common/storage-sas-overview.md) for the [database scoped credential](/sql/t-sql/statements/create-credential-transact-sql#d-creating-a-credential-using-a-sas-token), when accessing Azure storage for bulk insert, `BACKUP` and `RESTORE` statements, or the `OPENROWSET` function. For example:
134+
Currently, the `DATABASE SCOPED CREDENTIAL` syntax is not supported with Managed Identity to authenticate to Azure Storage. Microsoft recommends using a [shared access signature](../../storage/common/storage-sas-overview.md) for the [database scoped credential](/sql/t-sql/statements/create-credential-transact-sql#d-creating-a-credential-using-a-sas-token), when accessing Azure Storage for bulk insert, `BACKUP` and `RESTORE` statements, or the `OPENROWSET` function. For example:
135135

136136
```sql
137137
CREATE DATABASE SCOPED CREDENTIAL sas_cred WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
@@ -279,6 +279,36 @@ using (var scope = new TransactionScope())
279279

280280
CLR modules in SQL Managed Instance and linked servers or distributed queries that reference a current instance sometimes can't resolve the IP of a local instance. This error is a transient issue.
281281

282+
### Transaction scope on two databases within the same instance isn't supported
283+
284+
**(Resolved in March 2020)** The `TransactionScope` class in .NET doesn't work if two queries are sent to two databases within the same instance under the same transaction scope:
285+
286+
```csharp
287+
using (var scope = new TransactionScope())
288+
{
289+
using (var conn1 = new SqlConnection("Server=quickstartbmi.neu15011648751ff.database.windows.net;Database=b;User ID=myuser;Password=mypassword;Encrypt=true"))
290+
{
291+
conn1.Open();
292+
SqlCommand cmd1 = conn1.CreateCommand();
293+
cmd1.CommandText = string.Format("insert into T1 values(1)");
294+
cmd1.ExecuteNonQuery();
295+
}
296+
297+
using (var conn2 = new SqlConnection("Server=quickstartbmi.neu15011648751ff.database.windows.net;Database=b;User ID=myuser;Password=mypassword;Encrypt=true"))
298+
{
299+
conn2.Open();
300+
var cmd2 = conn2.CreateCommand();
301+
cmd2.CommandText = string.Format("insert into b.dbo.T2 values(2)"); cmd2.ExecuteNonQuery();
302+
}
303+
304+
scope.Complete();
305+
}
306+
307+
```
308+
309+
**Workaround (not needed since March 2020)**: Use [SqlConnection.ChangeDatabase(String)](/dotnet/api/system.data.sqlclient.sqlconnection.changedatabase) to use another database in a connection context instead of using two connections.
310+
311+
282312
## No resolution
283313

284314
### Misleading error message on Azure portal suggesting recreation of the Service Principal
@@ -316,36 +346,6 @@ The `tempdb` database is always split into 12 data files, and the file structure
316346

317347
Error logs that are available in SQL Managed Instance aren't persisted, and their size isn't included in the maximum storage limit. Error logs might be automatically erased if failover occurs. There might be gaps in the error log history because SQL Managed Instance was moved several times on several virtual machines.
318348

319-
### Transaction scope on two databases within the same instance isn't supported
320-
321-
**(Resolved in March 2020)** The `TransactionScope` class in .NET doesn't work if two queries are sent to two databases within the same instance under the same transaction scope:
322-
323-
```csharp
324-
using (var scope = new TransactionScope())
325-
{
326-
using (var conn1 = new SqlConnection("Server=quickstartbmi.neu15011648751ff.database.windows.net;Database=b;User ID=myuser;Password=mypassword;Encrypt=true"))
327-
{
328-
conn1.Open();
329-
SqlCommand cmd1 = conn1.CreateCommand();
330-
cmd1.CommandText = string.Format("insert into T1 values(1)");
331-
cmd1.ExecuteNonQuery();
332-
}
333-
334-
using (var conn2 = new SqlConnection("Server=quickstartbmi.neu15011648751ff.database.windows.net;Database=b;User ID=myuser;Password=mypassword;Encrypt=true"))
335-
{
336-
conn2.Open();
337-
var cmd2 = conn2.CreateCommand();
338-
cmd2.CommandText = string.Format("insert into b.dbo.T2 values(2)"); cmd2.ExecuteNonQuery();
339-
}
340-
341-
scope.Complete();
342-
}
343-
344-
```
345-
346-
**Workaround (not needed since March 2020)**: Use [SqlConnection.ChangeDatabase(String)](/dotnet/api/system.data.sqlclient.sqlconnection.changedatabase) to use another database in a connection context instead of using two connections.
347-
348-
349349
## Contribute to content
350350

351351
To contribute to the Azure SQL documentation, see the [Docs contributor guide](/contribute/).

‎articles/azure-sql/managed-instance/restore-sample-database-quickstart.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -45,69 +45,69 @@ In SSMS, follow these steps to restore the Wide World Importers database to SQL
4545
1. Open SSMS and connect to your managed instance.
4646
2. In **Object Explorer**, right-click the databases of your managed instance and select **Restore Database** to open the restore wizard.
4747

48-
![Screenshot that shows opening the restore wizard.](./media/restore-sample-database-quickstart/restore-wizard-start.png)
48+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-start.png" alt-text="Screenshot that shows opening the restore wizard.":::
4949

5050
3. In the new restore wizard, select the ellipsis (**...**) to select the source of the backup file to use.
5151

52-
![Screenshot that shows opening a new restore wizard window.](./media/restore-sample-database-quickstart/new-restore-wizard.png)
52+
:::image type="content" source="./media/restore-sample-database-quickstart/new-restore-wizard.png" alt-text="Screenshot that shows opening a new restore wizard window.":::
5353

5454
4. In **Select backup devices**, select **Add**. In **Backup media type**, **URL** is the only option because it is the only source type supported. Select **OK**.
5555

56-
![Screenshot that shows selecting the device.](./media/restore-sample-database-quickstart/restore-wizard-select-device.png)
56+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-select-device.png" alt-text="Screenshot that shows selecting the device.":::
5757

5858
5. In **Select a Backup File Location**, you can choose from three options to provide information about backup files are located:
5959
- Select a pre-registered storage container from the dropdown.
6060
- Enter a new storage container and a shared access signature. (A new SQL credential will be registered for you.)
6161
- Select **Add** to browse more storage containers from your Azure subscription.
6262

63-
![Screenshot that shows selecting the backup file location.](./media/restore-sample-database-quickstart/restore-wizard-backup-file-location.png)
63+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-backup-file-location.png" alt-text="Screenshot that shows selecting the backup file location.":::
6464

6565
Complete the next steps if you select the **Add** button. If you use a different method to provide the backup file location, go to step 12.
6666
6. In **Connect to a Microsoft Subscription**, select **Sign in** to sign in to your Azure subscription:
6767

68-
![Screenshot that shows Azure subscription sign-in.](./media/restore-sample-database-quickstart/restore-wizard-connect-subscription-sign-in.png)
68+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-connect-subscription-sign-in.png" alt-text="Screenshot that shows Azure subscription sign-in.":::
6969

7070
7. Sign in to your Microsoft Account to initiate the session in Azure:
7171

72-
![Screenshot that shows signing in to the Azure session.](./media/restore-sample-database-quickstart/restore-wizard-sign-in-session.png)
72+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-sign-in-session.png" alt-text="Screenshot that shows signing in to the Azure session.":::
7373

7474
8. Select the subscription where the storage account with the backup files is located:
7575

76-
![Screenshot that shows selecting the subscription.](./media/restore-sample-database-quickstart/restore-wizard-select-subscription.png)
76+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-select-subscription.png" alt-text="Screenshot that shows selecting the subscription.":::
7777

7878
9. Select the storage account where the backup files are located:
7979

80-
![Screenshot that shows the storage account.](./media/restore-sample-database-quickstart/restore-wizard-select-storage-account.png)
80+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-select-storage-account.png" alt-text="Screenshot that shows the storage account.":::
8181

8282
10. Select the blob container where the backup files are located:
8383

84-
![Select Blob container](./media/restore-sample-database-quickstart/restore-wizard-select-container.png)
84+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-select-container.png" alt-text="Select Blob container":::
8585

8686
11. Specify the expiration date of the shared access policy and select **Create Credential**. A shared access signature with the correct permissions is created. Select **OK**.
8787

88-
![Screenshot that shows generating the shared access signature.](./media/restore-sample-database-quickstart/restore-wizard-generate-shared-access-signature.png)
88+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-generate-shared-access-signature.png" alt-text="Screenshot that shows generating the shared access signature.":::
8989

9090
12. In the left pane, expand the folder structure to show the folder where the backup files are located. Select all the backup files that are related to the backup set to be restored, and then select **OK**:
9191

92-
![Screenshot that shows the backup file selection.](./media/restore-sample-database-quickstart/restore-wizard-backup-file-selection.png)
92+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-backup-file-selection.png" alt-text="Screenshot that shows the backup file selection.":::
9393

9494
SSMS validates the backup set. The process takes up to a few seconds depending on the size of the backup set.
9595

9696
13. If the backup is validated, specify the destination database name or leave the database name of the backup set, and then select **OK**:
9797

98-
![Screenshot that shows starting the restore.](./media/restore-sample-database-quickstart/restore-wizard-start-restore.png)
98+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-start-restore.png" alt-text="Screenshot that shows starting the restore.":::
9999

100100
The restore starts. The duration depends on the size of the backup set.
101101

102-
![Screenshot that shows running the restore.](./media/restore-sample-database-quickstart/restore-wizard-running-restore.png)
102+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-running-restore.png" alt-text="Screenshot that shows running the restore.":::
103103

104104
14. When the restore finishes, a dialog shows that it was successful. Select **OK**.
105105

106-
![Screenshot that shows the finished restore.](./media/restore-sample-database-quickstart/restore-wizard-finish-restore.png)
106+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-finish-restore.png" alt-text="Screenshot that shows the finished restore.":::
107107

108108
15. Check the restored database in Object Explorer:
109109

110-
![Screenshot that shows the restored database.](./media/restore-sample-database-quickstart/restore-wizard-restored-database.png)
110+
:::image type="content" source="./media/restore-sample-database-quickstart/restore-wizard-restored-database.png" alt-text="Screenshot that shows the restored database.":::
111111

112112

113113
## Restore from a backup file using T-SQL
@@ -127,7 +127,7 @@ In SQL Server Management Studio, follow these steps to restore the Wide World Im
127127
, SECRET = 'sv=2017-11-09&ss=bfqt&srt=sco&sp=rwdlacup&se=2028-09-06T02:52:55Z&st=2018-09-04T18:52:55Z&spr=https&sig=WOTiM%2FS4GVF%2FEEs9DGQR9Im0W%2BwndxW2CQ7%2B5fHd7Is%3D'
128128
```
129129

130-
![create credential](./media/restore-sample-database-quickstart/credential.png)
130+
:::image type="content" source="./media/restore-sample-database-quickstart/credential.png" alt-text="create credential":::
131131

132132
4. To check your credential, run the following script, which uses a [container](https://azure.microsoft.com/services/container-instances/) URL to get a backup file list.
133133

@@ -136,7 +136,7 @@ In SQL Server Management Studio, follow these steps to restore the Wide World Im
136136
'https://mitutorials.blob.core.windows.net/databases/WideWorldImporters-Standard.bak'
137137
```
138138

139-
![file list](./media/restore-sample-database-quickstart/file-list.png)
139+
:::image type="content" source="./media/restore-sample-database-quickstart/file-list.png" alt-text="file list":::
140140

141141
5. Run the following script to restore the Wide World Importers database.
142142

@@ -145,7 +145,7 @@ In SQL Server Management Studio, follow these steps to restore the Wide World Im
145145
'https://mitutorials.blob.core.windows.net/databases/WideWorldImporters-Standard.bak'
146146
```
147147

148-
![Screenshot shows the script running in Object Explorer with a success message.](./media/restore-sample-database-quickstart/restore.png)
148+
:::image type="content" source="./media/restore-sample-database-quickstart/restore.png" alt-text="Screenshot shows the script running in Object Explorer with a success message.":::
149149

150150
6. Run the following script to track the status of your restore.
151151

0 commit comments

Comments
 (0)