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: azure-sql/multi-model-features.md
+17-2Lines changed: 17 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Microsoft Azure SQL enables you to work with multiple data models i
4
4
author: WilliamDAssafMSFT
5
5
ms.author: wiassaf
6
6
ms.reviewer: mathoma, urmilano, damauri
7
-
ms.date: 11/06/2024
7
+
ms.date: 03/09/2026
8
8
ms.service: azure-sql
9
9
ms.subservice: service-overview
10
10
ms.topic: concept-article
@@ -113,7 +113,7 @@ Spatial features in Azure SQL enable you to store geometrical and geographical d
113
113
114
114
## Key-value pairs
115
115
116
-
Azure SQL products don't have specialized types or structures that support key-value pairs, because key-value structures can be natively represented as standard relational tables:
116
+
Azure SQL products don't have specialized types or structures that support key-value pairs, because [key-value structures can be natively represented](https://devblogs.microsoft.com/azure-sql/azure-sql-database-as-a-key-value-store/) as standard relational tables:
117
117
118
118
```sql
119
119
CREATETABLECollection (
@@ -129,6 +129,20 @@ You can customize this key-value structure to fit your needs without any constra
129
129
130
130
For an example of how a relational model can be effectively used as a key-value pair solution in practice, see [How bwin is using SQL Server 2016 In-Memory OLTP to achieve unprecedented performance and scale](/archive/blogs/sqlcat/how-bwin-is-using-sql-server-2016-in-memory-oltp-to-achieve-unprecedented-performance-and-scale). In this case study, bwin used a relational model for its ASP.NET caching solution to achieve 1.2 million batches per second.
131
131
132
+
## Vector
133
+
134
+
Azure SQL products support the **vector** data type and vector functions underlying [modern AI applications](/azure/azure-sql/database/ai-artificial-intelligence-intelligent-applications). The SQL Database Engine can store and query both structured and unstructured data, and perform vector search on that data. Vector search enables approximate nearest neighbor search using [vectors and vector indexes](/sql/sql-server/ai/vectors).
135
+
136
+
Vectors are ordered arrays of numbers (typically floating point values) that represent information about some data. For example, an image can be represented as a vector of pixel values, or a string of text can be represented as a vector of ASCII values. The process to turn data into a vector is called vectorization. The **[vector](/sql/t-sql/data-types/vector-data-type)** data type in SQL Server can store these arrays of numbers efficiently.
137
+
138
+
*Embeddings* are vectors that represent important features of data. Embeddings are often learned by using a deep learning model, and machine learning and AI models utilize them as features. Embeddings can also capture semantic similarity between concepts. For example, in generating an embedding for the words `person` and `human`, we expect their embeddings (vector representation) to be similar in value since the words are also semantically similar. Once embeddings are generated, they can be stored in a SQL Server database. This allows you to store the embeddings alongside the data they represent, and to perform vector search queries to find similar data points.
139
+
140
+
Azure OpenAI features models to create embeddings from text data. The service breaks text out into tokens and generates embeddings using models pretrained by OpenAI. To learn more, see [Creating embeddings with Azure OpenAI](/azure/ai-services/openai/concepts/understand-embeddings).
-[Azure SQL Database Vector Search Samples on GitHub](https://github.com/Azure-Samples/azure-sql-db-vector-search)
145
+
132
146
## Next steps
133
147
134
148
Multi-model capabilities are core SQL Server database engine features that are shared among Azure SQL products. To learn more about these features, see these articles:
@@ -138,3 +152,4 @@ Multi-model capabilities are core SQL Server database engine features that are s
138
152
-[Spatial data in SQL Server](/sql/relational-databases/spatial/spatial-data-sql-server)
139
153
-[XML data in SQL Server](/sql/relational-databases/xml/xml-data-sql-server)
140
154
-[Key-value store performance in Azure SQL Database](https://devblogs.microsoft.com/azure-sql/azure-sql-database-as-a-key-value-store/)
155
+
-[Vectors and vector indexes](/sql/sql-server/ai/vectors)
Copy file name to clipboardExpand all lines: docs/big-data-cluster/big-data-options.md
-32Lines changed: 0 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,38 +80,6 @@ For more information on building scalable architectures, see [Build a scalable s
80
80
81
81
## In-cloud
82
82
83
-
### Azure SQL with Synapse
84
-
85
-
You can replace the functionality of SQL Server Big Data Clusters by using one or more Azure SQL database options for operational data, and Microsoft Azure Synapse for your analytic workloads.
86
-
87
-
Microsoft Azure Synapse is an enterprise analytics service that accelerates time to insight across data warehouses and big data systems, using distributed processing and data constructs. Azure Synapse brings together SQL technologies used in enterprise data warehousing, Spark technologies used for big data, Pipelines for data integration and ETL/ELT, and deep integration with other Azure services such as Power BI, Cosmos DB, and Azure Machine Learning.
88
-
89
-
Use Microsoft Azure Synapse as a replacement for [!INCLUDE [ssbigdataclusters-ver15](../includes/ssbigdataclusters-ver15.md)] when you need to:
90
-
91
-
- Use both serverless and dedicated resource models. For predictable performance and cost, create dedicated SQL pools to reserve processing power for data stored in SQL tables.
92
-
- Process unplanned or "burst" workloads, access an always-available, serverless SQL endpoint.
93
-
- Use built-in streaming capabilities to land data from cloud data sources into SQL tables.
94
-
- Integrate AI with SQL by using machine learning models to score data using the T-SQL PREDICT function.
95
-
- Use ML models with SparkML algorithms and Azure Machine Learning integration for Apache Spark 2.4 supported for Linux Foundation Delta Lake.
96
-
- Use a simplified resource model that frees you from having to worry about managing clusters.
97
-
- Process data that requires fast Spark start-up and aggressive autoscaling.
98
-
- Process data using.NET for Spark allowing you to reuse your C\# expertise and existing .NET code within a Spark application.
99
-
- Work with tables defined on files in the data lake, seamlessly consumed by either Spark or Hive.
100
-
- Use SQL with Spark to directly explore and analyze Parquet, CSV, TSV, and JSON files stored in a data lake.
101
-
- Enable fast, scalable data loading between SQL and Spark databases.
102
-
- Ingest data from 90+ data sources.
103
-
- Enable "Code-Free" ETL with Data flow activities.
104
-
- Orchestrate notebooks, Spark jobs, stored procedures, SQL scripts, and more.
105
-
- Monitor resources, usage, and users across SQL and Spark.
106
-
- Use Role-based access control to simplify access to analytics resources.
107
-
- Write SQL or Spark code and integrate with enterprise CI/CD processes.
108
-
109
-
The architecture of Microsoft Azure Synapse is as follows:
For more information on Microsoft Azure Synapse, see [What is Azure Synapse Analytics?](/azure/synapse-analytics/overview-what-is)
114
-
115
83
### Azure SQL plus Azure Machine Learning
116
84
117
85
You can replace the functionality of SQL Server Big Data Clusters by using one or more Azure SQL database options for operational data, and Microsoft Azure Machine Learning for your predictive workloads.
Copy file name to clipboardExpand all lines: docs/database-engine/install-windows/install-sql-server.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,6 @@ For other deployment scenarios, see:
25
25
26
26
-[Installation guidance for SQL Server on Linux](../../linux/sql-server-linux-setup.md)
27
27
-[Deploy and connect to SQL Server Linux containers](../../linux/sql-server-linux-docker-container-deployment.md)
28
-
-[Kubernetes - Big Data Clusters](../../big-data-cluster/deploy-get-started.md) ([!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] only)
29
28
30
29
Beginning with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] is only available as a 64-bit application. Here are important details about how to get [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] and how to install it.
31
30
@@ -103,7 +102,7 @@ Other [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] components can
103
102
104
103
| Article | Description |
105
104
| --- | --- |
106
-
|[Install SQL Server Database Engine](install-sql-server-database-engine.md)| Install and configure the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)]. |
105
+
|[Install SQL Server Database Engine](install-sql-server-database-engine.md)| Install and configure the [[!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)]](../sql-database-engine.md). |
107
106
|[Install SQL Server replication](install-sql-server-replication.md)| Install and configure [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Replication. |
108
107
|[Install Distributed Replay](../../tools/distributed-replay/install-distributed-replay.md)<sup>1</sup> | Lists articles to install the Distributed Replay feature. |
109
108
|[SQL Server Management Tools](/ssms/install/install)| Install and configure [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] management tools. |
0 commit comments