Skip to content

Commit f9bf1cb

Browse files
authored
Merge pull request #20314 from MicrosoftDocs/release-2016-sp3
Publish clarification for SP3
2 parents b99d858 + 71205b8 commit f9bf1cb

2 files changed

Lines changed: 37 additions & 0 deletions

File tree

docs/machine-learning/troubleshooting/known-issues-for-sql-server-machine-learning-services.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -260,6 +260,23 @@ Disable FIPS before the installation of SQL Server 2019 with the feature **Machi
260260

261261
**Applies to:** SQL Server 2019
262262

263+
### 16. R Services using specific algorithms, streaming, or partitioning
264+
265+
- **Issue**: The following limitations apply on [!INCLUDE[sssql17-md](../../includes/sssql17-md.md)] with runtime upgrade. This issue applies to Enterprise Edition.
266+
267+
- Parallelism: `RevoScaleR` and `MicrosoftML` algorithm thread parallelism for scenarios are limited to maximum of 2 threads.
268+
- Streaming & partitioning: Scenarios involving `@r_rowsPerRead` parameter passed to T-SQL `sp_execute_external_script` is not applied.
269+
- Streaming & partitioning: `RevoScaleR` and `MicrosoftML` data sources (i.e. `ODBC`, `XDF`) does not support reading rows in chunks for training or scoring scenarios. These scenarios always bring all data to memory for computation and the operations are memory bound
270+
271+
- **Solution**: The best solution is to upgrade to [!INCLUDE[sssql19-md](../../includes/sssql19-md.md)]. Alternatively you can continue to use [!INCLUDE[sssql17-md](../../includes/sssql17-md.md)] with runtime upgrade configured using [RegisterRext.exe /configure](../install/change-default-language-runtime-version.md), after you complete the following tasks.
272+
273+
1. Edit registry to create a key `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\150` and add a value `SharedCode` with data `C:\Program Files\Microsoft SQL Server\150\Shared` or the instance shared directory, as configured.
274+
1. Create a folder `C:\Program Files\Microsoft SQL Server\150\Shared and copy instapi140.dll` from the folder `C:\Program Files\Microsoft SQL Server\140\Shared` to the newly created folder.
275+
1. Rename the `instapi140.dll` to `instapi150.dll` in the new folder `C:\Program Files\Microsoft SQL Server\150\Shared`.
276+
277+
> [!IMPORTANT]
278+
> If you do the steps above, you must manually remove the added key prior to upgrading to a later version of SQL Server.
279+
263280
## R script execution issues
264281

265282
This section contains known issues that are specific to running R on SQL Server, as well as some issues that are related to the R libraries and tools published by Microsoft, including RevoScaleR.

docs/sql-server/sql-server-2016-release-notes.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,26 @@ Supportability and diagnostics related improvements included in [!INCLUDE[sssql1
5656

5757
This section identifies issues which may occur after you apply [!INCLUDE[sssql16-md](../includes/sssql16-md.md)] SP3.
5858

59+
### R Services using specific algorithms, streaming, or partitioning
60+
61+
- **Issue**: The following limitations apply on [!INCLUDE[sssql16-md](../includes/sssql16-md.md)] with runtime upgrade configured using [RegisterRext.exe /configure](../machine-learning/install/change-default-language-runtime-version.md) or with SP3 slipstream install. This issue applies to Enterprise Edition.
62+
63+
- Parallelism: `RevoScaleR` and `MicrosoftML` algorithm thread parallelism for scenarios are limited to maximum of 2 threads.
64+
- Streaming & partitioning: Scenarios involving `@r_rowsPerRead` parameter passed to T-SQL `sp_execute_external_script` is not applied.
65+
- Streaming & partitioning: `RevoScaleR` and `MicrosoftML` data sources (i.e. `ODBC`, `XDF`) does not support reading rows in chunks for training or scoring scenarios. These scenarios always bring all data to memory for computation and the operations are memory bound
66+
67+
- **Solution**: The best solution is to upgrade to [!INCLUDE[sssql19-md](../includes/sssql19-md.md)]. Alternatively you can continue to use [!INCLUDE[sssql16-md](../includes/sssql16-md.md)] SP3, after you complete the following tasks.
68+
69+
1. Edit registry to create a key `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\150` and add a value `SharedCode` with data `C:\Program Files\Microsoft SQL Server\150\Shared` or the shared directory as configured for the instance.
70+
71+
1. Create a folder `C:\Program Files\Microsoft SQL Server\150\Shared and copy instapi130.dll` from the folder `C:\Program Files\Microsoft SQL Server\130\Shared` to the newly created folder.
72+
1. Rename the `instapi130.dll` to `instapi150.dll` in the new folder `C:\Program Files\Microsoft SQL Server\150\Shared`.
73+
74+
> [!IMPORTANT]
75+
> If you do the steps above, you must manually remove the added key prior to upgrading to a later version of SQL Server.
76+
77+
For additional information, see [Change R runtime version in SQL Server 2016](../machine-learning/install/change-default-language-runtime-version.md#change-r-runtime-version-in-sql-server-2016).
78+
5979
### Change Tracking cleanup errors
6080

6181
- **Issue**: The following error message occurs after you run a change tracking cleanup stored procedure `sp_flush_commit_table_on_demand` or `sp_flush_CT_internal_table_on_demand`:

0 commit comments

Comments
 (0)