Skip to content

Commit 9e9b679

Browse files
authored
Merge pull request #113596 from MikeRys/patch-2
Removed SQL Pool content
2 parents 001340a + 6acc7b9 commit 9e9b679

File tree

1 file changed

+5
-26
lines changed

1 file changed

+5
-26
lines changed

articles/synapse-analytics/metadata/database.md

Lines changed: 5 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -6,35 +6,29 @@ author: MikeRys
66
ms.service: synapse-analytics
77
ms.topic: overview
88
ms.subservice:
9-
ms.date: 04/15/2020
9+
ms.date: 05/01/2020
1010
ms.author: mrys
1111
ms.reviewer: jrasnick
1212
---
1313

1414
# Azure Synapse Analytics shared database
1515

16-
Azure Synapse Analytics allows the different computational workspace engines to share databases and tables between its Spark pools (preview), SQL on-demand (preview) engine, and SQL pools.
16+
Azure Synapse Analytics allows the different computational workspace engines to share databases and tables between its Spark pools (preview) and SQL on-demand (preview) engine.
1717

1818
[!INCLUDE [synapse-analytics-preview-terms](../../../includes/synapse-analytics-preview-terms.md)]
1919

2020
A database created with a Spark job will become visible with that same name to all current and future Spark pools (preview) in the workspace as well as the SQL on-demand engine.
2121

22-
If there are SQL pools in the workspace that have metadata synchronization enabled, or if you create a new SQL pool with the metadata synchronization enabled, these Spark created databases are automatically mapped into special schemas in the SQL pool database.
22+
The Spark default database, called `default`, will also be visible in the SQL on-demand context as a database called `default`.
2323

24-
Each schema is named after the Spark database name with an additional `$` prefix. Both the external and managed tables in the Spark-generated database are exposed as external tables in the corresponding special schema.
25-
26-
The Spark default database, called `default`, will also be visible in the SQL on-demand context as a database called `default`, and in any of the SQL pool databases with metadata synchronization turned on as the schema `$default`.
27-
28-
Since the databases are synchronized to SQL on-demand and the SQL pools asynchronously, there will be a delay until they appear.
24+
Since the databases are synchronized to SQL on-demand asynchronously, there will be a delay until they appear.
2925

3026
## Manage a Spark created database
3127

3228
Use Spark to manage Spark created databases. For example, delete it through a Spark pool job, and create tables in it from Spark.
3329

3430
If you create objects in a Spark created database using SQL on-demand, or try to drop the database, the operation will succeed. But, the original Spark database won't be changed.
3531

36-
If you try to drop the synchronized schema in a SQL pool, or try to create a table in it, Azure returns an error.
37-
3832
## Handling of name conflicts
3933

4034
If the name of a Spark database conflicts with the name of an existing SQL on-demand database, a suffix is appended in SQL on-demand to the Spark database. The suffix in SQL on-demand is `_<workspace name>-ondemand-DefaultSparkConnector`.
@@ -46,7 +40,7 @@ For example, if a Spark database called `mydb` gets created in the Azure Synapse
4640
4741
## Security model
4842

49-
The Spark databases and tables, along with their synchronized representations in the SQL engines will be secured at the underlying storage level.
43+
The Spark databases and tables, along with their synchronized representations in the SQL engine will be secured at the underlying storage level.
5044

5145
The security principal who creates a database is considered the owner of that database, and has all the rights to the database and its objects.
5246

@@ -74,22 +68,7 @@ SELECT * FROM sys.databases;
7468

7569
Verify that `mytestdb` is included in the results.
7670

77-
### Exposing a Spark database in a SQL pool
78-
79-
With the database created in the previous example, now create a SQL pool in your workspace named `mysqlpool` that enables metadata synchronization.
80-
81-
Run the following statement against the `mysqlpool` SQL pool:
82-
83-
```sql
84-
SELECT * FROM sys.schema;
85-
```
86-
87-
Verify the schema for the newly created database in the results.
88-
8971
## Next steps
9072

9173
- [Learn more about Azure Synapse Analytics' shared metadata](overview.md)
9274
- [Learn more about Azure Synapse Analytics' shared metadata Tables](table.md)
93-
94-
<!-- - [Learn more about the Synchronization with SQL on-demand](overview.md)
95-
- [Learn more about the Synchronization with SQL pools](overview.md)-->

0 commit comments

Comments
 (0)