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
|[When using SQL Server authentication, usernames with '@' are not supported](#when-using-sql-server-authentication-usernames-with--are-not-supported)|Oct 2021|||
26
+
|[When using SQL Server authentication, usernames with '@' are not supported](#when-using-sql-server-authentication-usernames-with--are-not-supported)|Oct 2021|Resolved|Feb 2022|
27
27
|[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||Oct 2021|
28
28
|[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||
29
29
|[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||
@@ -284,10 +284,6 @@ using (var scope = new TransactionScope())
284
284
285
285
## No resolution
286
286
287
-
### When using SQL Server authentication, usernames with '@' are not supported
288
-
289
-
Usernames that contain the '@' symbol in the middle (e.g. 'abc@xy') are not able to log in using SQL Server authentication.
290
-
291
287
### Azure AD logins and users are not supported in SSDT
292
288
293
289
SQL Server Data Tools don't fully support Azure AD logins and users.
@@ -313,6 +309,10 @@ Error logs that are available in SQL Managed Instance aren't persisted, and thei
313
309
314
310
## Resolved
315
311
312
+
### When using SQL Server authentication, usernames with '@' are not supported
313
+
314
+
Usernames that contain the '@' symbol in the middle (e.g. 'abc@xy') are not able to log in using SQL Server authentication.
315
+
316
316
### Restoring manual backup without CHECKSUM might fail
317
317
318
318
In certain circumstances manual backup of databases that was made on a managed instance without CHECKSUM might fail to be restored. In such cases, retry restoring the backup until you're successful.
0 commit comments