Skip to content

Commit 7435ea9

Browse files
PRMerger7PRMerger7
authored
Merge pull request MicrosoftDocs#85828 from jovanpop-msft/patch-103
Added AAD impersonation, moved TDE backup issue
2 parents 9fdca4c + 632c13f commit 7435ea9

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

‎articles/sql-database/sql-database-managed-instance-transact-sql-information.md

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,7 @@ Managed instances have automatic backups, so users can create full database `COP
5757
Limitations:
5858

5959
- With a managed instance, you can back up an instance database to a backup with up to 32 stripes, which is enough for databases up to 4 TB if backup compression is used.
60+
- You can't execute `BACKUP DATABASE ... WITH COPY_ONLY` on a database that's encrypted with service-managed Transparent Data Encryption (TDE). Service-managed TDE forces backups to be encrypted with an internal TDE key. The key can't be exported, so you can't restore the backup. Use automatic backups and point-in-time restore, or use [customer-managed (BYOK) TDE](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-azure-sql#customer-managed-transparent-data-encryption---bring-your-own-key) instead. You also can disable encryption on the database.
6061
- The maximum backup stripe size by using the `BACKUP` command in a managed instance is 195 GB, which is the maximum blob size. Increase the number of stripes in the backup command to reduce individual stripe size and stay within this limit.
6162

6263
> [!TIP]
@@ -533,6 +534,14 @@ Cross-database Service Broker dialogs fail to deliver the messages after change
533534

534535
**Workaround:** Stop any activity that uses cross-database Service Broker dialog conversations before updating service tier and re-initialize them after.
535536

537+
### Some AAD login types cannot be impersonated
538+
539+
**Date:** July 2019
540+
541+
Impersonation using `EXECUTE AS USER` or `EXECUTE AS LOGIN` of following AAD principals is not supported:
542+
- Aliased AAD users. The following error is returned in this case `15517`.
543+
- AAD logins and users based on AAD applications or service principals. The following errors are returned in this case `15517` and `15406`.
544+
536545
### @query parameter not supported in sp_send_db_mail
537546

538547
**Date:** April 2019
@@ -541,13 +550,13 @@ The `@query` parameter in the [sp_send_db_mail](https://docs.microsoft.com/sql/r
541550

542551
### AAD logins and users are not supported in tools
543552

544-
**Date:** April 2019
553+
**Date:** Jan 2019
545554

546555
SQL Server Management Studio and SQL Server Data Tools don't fuly support Azure Acctive directory logins and users.
547556
- Using Azure AD server principals (logins) and users (public preview) with SQL Server Data Tools currently isn't supported.
548557
- Scripting for Azure AD server principals (logins) and users (public preview) isn't supported in SQL Server Management Studio.
549558

550-
### TEMPDB structure is re-created
559+
### TEMPDB structure and content is re-created
551560

552561
The `tempdb` database is always split into 12 data files and the file structure cannot be changed. The maximum size per file can't be changed, and new files cannot be added to `tempdb`. `Tempdb` is always re-created as an empty database when the instance starts or fails over, and any changes made in `tempdb` will not be preserved.
553562

@@ -619,12 +628,6 @@ CLR modules placed in a managed instance and linked servers or distributed queri
619628

620629
**Workaround:** Use context connections in a CLR module if possible.
621630

622-
### TDE-encrypted databases with a service-managed key don't support user-initiated backups
623-
624-
You can't execute `BACKUP DATABASE ... WITH COPY_ONLY` on a database that's encrypted with service-managed Transparent Data Encryption (TDE). Service-managed TDE forces backups to be encrypted with an internal TDE key. The key can't be exported, so you can't restore the backup.
625-
626-
**Workaround:** Use automatic backups and point-in-time restore, or use [customer-managed (BYOK) TDE](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-azure-sql#customer-managed-transparent-data-encryption---bring-your-own-key) instead. You also can disable encryption on the database.
627-
628631
## Next steps
629632

630633
- For more information about managed instances, see [What is a managed instance?](sql-database-managed-instance.md)

0 commit comments

Comments
 (0)