Skip to content

Commit 67b8bd3

Browse files
Merge pull request #35441 from yorek/rc1-dm-fix
added note about known bug
2 parents 2ce5603 + 68490a9 commit 67b8bd3

2 files changed

Lines changed: 22 additions & 3 deletions

File tree

docs/sql-server/sql-server-2025-known-issues.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ This article describes known issues for [!INCLUDE [sssql25-md](../includes/sssql
2929
- [Local ONNX models not supported on Linux operating systems](#local-onnx-models-not-supported-on-linux-operating-systems)
3030
- [PBKDF2 hashing algorithm can affect login performance](#pbkdf2-hashing-algorithm-can-affect-login-performance)
3131
- [Access violation exception can occur on readable secondary replicas under certain conditions](#access-violation-exception-can-occur-on-readable-secondary-replicas-under-certain-conditions)
32+
- [Vector index](#vector-index)
3233

3334
## Windows Arm64 not supported
3435

@@ -131,6 +132,15 @@ ALTER DATABASE SCOPED CONFIGURATION FOR SECONDARY
131132
SET PARAMETER_SENSITIVE_PLAN_OPTIMIZATION = OFF;
132133
```
133134

135+
## Vector index
136+
137+
Currently, when you create a vector index on some datasets, it may return the following errors:
138+
139+
- Error 9829: `STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.`
140+
- 42234: `Internal SQL error during DiskANN graph build`
141+
142+
A fix has been identified and will be part of a future release of [!INCLUDE [sssql25-md](../includes/sssql25-md.md)].
143+
134144
## Related content
135145

136146
- [What's new in SQL Server 2025 Preview](what-s-new-in-sql-server-2025.md)

docs/t-sql/statements/create-vector-index-transact-sql.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,19 +71,19 @@ Table on which the index is created. It must be a base table. Views, temporary t
7171

7272
Column to use to create the vector index. It must be of **vector** type.
7373

74-
### METRIC = { 'cosine' | 'dot' | 'euclidean' }
74+
### METRIC
7575

7676
A string with the name of the distance metric to use to calculate the distance between the two given vectors. The following distance metrics are supported:
7777

7878
- `cosine` - Cosine distance
7979
- `euclidean` - Euclidean distance
8080
- `dot` - (Negative) Dot product
8181

82-
## TYPE = 'DiskANN'
82+
### TYPE
8383

8484
The type of [ANN algorithm](../../sql-server/ai/vectors.md#approximate-vector-index-and-vector-search-approximate-nearest-neighbors) used to build the index. Only `DiskANN` is currently supported. DiskANN is the default value.
8585

86-
## MAXDOP = *max_degree_of_parallelism*
86+
### MAXDOP
8787

8888
Overrides the **max degree of parallelism** configuration option for the index operation. For more information, see [Max degree of parallelism](../../database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md). Use `MAXDOP` to limit the degree of parallelism and the resulting resource consumption for an index build operation.
8989

@@ -115,6 +115,15 @@ The current preview has the following limitations:
115115
- A table with a vector index becomes read only. No data modification is allowed while the vector index is present on the table.
116116
- Vector indexes aren't replicated to subscribers.
117117

118+
## Known issues
119+
120+
Currently, when you create a vector index on some datasets, it may return the following errors:
121+
122+
- Error 9829: `STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.`
123+
- 42234: `Internal SQL error during DiskANN graph build`
124+
125+
For more information, review [Known issues](../../sql-server/sql-server-2025-known-issues.md#vector-index).
126+
118127
## Permissions
119128

120129
The user must have `ALTER` permission on the table.

0 commit comments

Comments
 (0)