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/synapse-analytics/sql/resources-self-help-sql-on-demand.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -695,7 +695,7 @@ If you are getting the error '*CREATE DATABASE failed. User database limit has b
695
695
696
696
### Please create a master key in the database or open the master key in the session before performing this operation.
697
697
698
-
If your query fails with the error message *Please create a master key in the database or open the master key in the session before performing this operation*, it means that your user database has no access to a master key at the moment.
698
+
If your query fails with the error message '*Please create a master key in the database or open the master key in the session before performing this operation*', it means that your user database has no access to a master key at the moment.
699
699
700
700
Most likely, you just created a new user database and did not create a master key yet.
701
701
@@ -905,7 +905,7 @@ If a user cannot access a lake house or Spark database, it might not have permis
905
905
Dataverse tables are accessing storage using the callers Azure AD identity. SQL user with high permissions might try to select data from a table, but the table would not be able to access Dataverse data. This scenario is not supported.
906
906
907
907
### Azure AD service principal login failures when SPI is creating a role assignment
908
-
If you want to create role assignment for Service Principal Identifier/Azure AD app using another SPI, or have already created one and it fails to login, you're probably receiving following error:
908
+
If you want to create role assignment for Service Principal Identifier/Azure AD app using another SPI, or have already created one and it fails to log in, you're probably receiving following error:
909
909
```
910
910
Login error: Login failed for user '<token-identified principal>'.
911
911
```
@@ -950,7 +950,7 @@ Connect to serverless SQL endpoint and verify that the external login with SID `
950
950
select name, convert(uniqueidentifier, sid) as sid, create_date
951
951
fromsys.server_principalswhere type in ('E', 'X')
952
952
```
953
-
or just try to login on serverless SQL endpoint using the just set admin app.
953
+
or just try to log in on serverless SQL endpoint using the just set admin app.
0 commit comments