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
Copy file name to clipboardExpand all lines: articles/sql-database/sql-database-release-notes.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,29 +74,29 @@ The following features are enabled in Managed instance deployment model in H1 20
74
74
75
75
|Issue |Date discovered |Status |Date resolved |
76
76
|---------|---------|---------|---------|
77
-
[Limitation of manual failover via portal for failover groups](#limitation-of-manual-failover-via-portal-for-failover-groups)|Jan 2020|Workaround|TBD|
78
-
[SQL Agent roles need explicit EXECUTE permissions for non-sysadmin logins](#in-memory-oltp-memory-limits-are-not-applied)|Dec 2019|Workaround|TBD|
79
-
[SQL Agent jobs can be interrupted by Agent process restart](#sql-agent-jobs-can-be-interrupted-by-agent-process-restart)|Dec 2019|No Workaround|TBD|
80
-
[AAD logins and users are not supported in SSDT](#aad-logins-and-users-are-not-supported-in-ssdt)|Nov 2019|No Workaround|TBD|
81
-
[In-memory OLTP memory limits are not applied](#in-memory-oltp-memory-limits-are-not-applied)|Oct 2019|Workaround|TBD|
82
-
[Wrong error returned while trying to remove a file that is not empty](#wrong-error-returned-while-trying-to-remove-a-file-that-is-not-empty)|Oct 2019|Workaround|TBD|
83
-
[Change service tier and create instance operations are blocked by ongoing database restore](#change-service-tier-and-create-instance-operations-are-blocked-by-ongoing-database-restore)|Sep 2019|Workaround|TBD|
84
-
[Resource Governor on Business Critical service tier might need to be reconfigured after failover](#resource-governor-on-business-critical-service-tier-might-need-to-be-reconfigured-after-failover)|Sep 2019|Workaround|TBD|
85
-
[Cross-database Service Broker dialogs must be re-initialized after service tier upgrade](#cross-database-service-broker-dialogs-must-be-re-initialized-after-service-tier-upgrade)|Aug 2019|Workaround|TBD|
86
-
[Impersonification of Azure AD login types is not supported](#impersonification-of-azure-ad-login-types-is-not-supported)|Jul 2019|No Workaround|TBD|
87
-
[@query parameter not supported in sp_send_db_mail](#-parameter-not-supported-in-sp_send_db_mail)|Apr 2019|No Workaround|TBD|
88
-
[Transactional Replication must be reconfigured after geo-failover](#transactional-replication-must-be-reconfigured-after-geo-failover)|Mar 2019|No Workaround|TBD|
89
-
[Temporary database is used during RESTORE operation](#temporary-database-is-used-during-restore-operation)|TBD|Workaround|TBD|
90
-
[TEMPDB structure and content is re-created](#tempdb-structure-and-content-is-re-created)|TBD|No Workaround|TBD|
91
-
[Exceeding storage space with small database files](#exceeding-storage-space-with-small-database-files)|TBD|Workaround|TBD|
92
-
[GUID values shown instead of database names](#guid-values-shown-instead-of-database-names)|TBD|No Workaround|TBD|
[Transaction scope on two databases within the same instance isn't supported](#transaction-scope-on-two-databases-within-the-same-instance-isnt-supported)|TBD|Workaround|TBD|
95
-
[CLR modules and linked servers sometimes can't reference a local IP address](#clr-modules-and-linked-servers-sometimes-cant-reference-a-local-ip-address)|TBD|Workaround|TBD|
96
-
Database consistency not verified using DBCC CHECKDB after restore database from Azure Blob Storage.|TBD|Resolved|Nov 2019|
97
-
point-in-time database restore from Business Critical tier to General Purpose tier will not succeed if source database contains in-memory OLTP objects.|TBD|Resolved|Oct 2019|
98
-
Database Mail feature with external (non-Azure) mail servers using secure connection|TBD|Resolved|Oct 2019|
99
-
Contained databases not supported in managed instance|TBD|Resolved|Aug 2019|
77
+
|[Limitation of manual failover via portal for failover groups](#limitation-of-manual-failover-via-portal-for-failover-groups)|Jan 2020|Workaround|TBD|
78
+
|[SQL Agent roles need explicit EXECUTE permissions for non-sysadmin logins](#in-memory-oltp-memory-limits-are-not-applied)|Dec 2019|Workaround|TBD|
79
+
|[SQL Agent jobs can be interrupted by Agent process restart](#sql-agent-jobs-can-be-interrupted-by-agent-process-restart)|Dec 2019|No Workaround|TBD|
80
+
|[AAD logins and users are not supported in SSDT](#aad-logins-and-users-are-not-supported-in-ssdt)|Nov 2019|No Workaround|TBD|
81
+
|[In-memory OLTP memory limits are not applied](#in-memory-oltp-memory-limits-are-not-applied)|Oct 2019|Workaround|TBD|
82
+
|[Wrong error returned while trying to remove a file that is not empty](#wrong-error-returned-while-trying-to-remove-a-file-that-is-not-empty)|Oct 2019|Workaround|TBD|
83
+
|[Change service tier and create instance operations are blocked by ongoing database restore](#change-service-tier-and-create-instance-operations-are-blocked-by-ongoing-database-restore)|Sep 2019|Workaround|TBD|
84
+
|[Resource Governor on Business Critical service tier might need to be reconfigured after failover](#resource-governor-on-business-critical-service-tier-might-need-to-be-reconfigured-after-failover)|Sep 2019|Workaround|TBD|
85
+
|[Cross-database Service Broker dialogs must be re-initialized after service tier upgrade](#cross-database-service-broker-dialogs-must-be-re-initialized-after-service-tier-upgrade)|Aug 2019|Workaround|TBD|
86
+
|[Impersonification of Azure AD login types is not supported](#impersonification-of-azure-ad-login-types-is-not-supported)|Jul 2019|No Workaround|TBD|
87
+
|[@query parameter not supported in sp_send_db_mail](#-parameter-not-supported-in-sp_send_db_mail)|Apr 2019|No Workaround|TBD|
88
+
|[Transactional Replication must be reconfigured after geo-failover](#transactional-replication-must-be-reconfigured-after-geo-failover)|Mar 2019|No Workaround|TBD|
89
+
|[Temporary database is used during RESTORE operation](#temporary-database-is-used-during-restore-operation)|TBD|Workaround|TBD|
90
+
|[TEMPDB structure and content is re-created](#tempdb-structure-and-content-is-re-created)|TBD|No Workaround|TBD|
91
+
|[Exceeding storage space with small database files](#exceeding-storage-space-with-small-database-files)|TBD|Workaround|TBD|
92
+
|[GUID values shown instead of database names](#guid-values-shown-instead-of-database-names)|TBD|No Workaround|TBD|
|[Transaction scope on two databases within the same instance isn't supported](#transaction-scope-on-two-databases-within-the-same-instance-isnt-supported)|TBD|Workaround|TBD|
95
+
|[CLR modules and linked servers sometimes can't reference a local IP address](#clr-modules-and-linked-servers-sometimes-cant-reference-a-local-ip-address)|TBD|Workaround|TBD|
96
+
|Database consistency not verified using DBCC CHECKDB after restore database from Azure Blob Storage.|TBD|Resolved|Nov 2019|
97
+
|Point-in-time database restore from Business Critical tier to General Purpose tier will not succeed if source database contains in-memory OLTP objects.|TBD|Resolved|Oct 2019|
98
+
|Database Mail feature with external (non-Azure) mail servers using secure connection|TBD|Resolved|Oct 2019|
99
+
|Contained databases not supported in managed instance|TBD|Resolved|Aug 2019|
100
100
101
101
### Limitation of manual failover via portal for failover groups
0 commit comments