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: docs/machine-learning/install/upgrade-r-and-python.md
+21-10Lines changed: 21 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Upgrade Python and R runtimes (binding)
3
3
description: Upgrade Python and R runtimes in SQL Server Machine Learning Services or SQL Server R Services using sqlbindr.exe to bind to Machine Learning Server.
4
4
ms.prod: sql
5
5
ms.technology: machine-learning-services
6
-
ms.date: 09/16/2020
6
+
ms.date: 09/30/2020
7
7
ms.topic: how-to
8
8
author: cawrites
9
9
ms.author: chadam
@@ -50,7 +50,7 @@ All of the binding can further be refreshed at each new major and minor release
50
50
51
51
The following tables are version maps. Each map shows package versions across releases. You can review upgrade paths when you bind to Microsoft Machine Learning Server (previously known as R Server, before the addition of Python support starting in Machine Learning Server 9.2.1).
52
52
53
-
The binding does not guarantee the latest version of R or Anaconda. When you bind to Microsoft Machine Learning Server, you get the R or Python version installed through Setup, which may not be the latest version available on the web.
53
+
The binding doesn't guarantee the latest version of R or Anaconda. When you bind to Microsoft Machine Learning Server, you get the R or Python version installed through Setup, which may not be the latest version available on the web.
[**SQL Server 2016 R Services**](../install/sql-r-services-windows-install.md)
@@ -106,7 +106,7 @@ Binding is reversible. You can revert to SQL Server servicing by [unbinding the
106
106
107
107
## Bind to Machine Learning Server using Setup
108
108
109
-
Follow the steps below to bind SQL Server to Microsoft Machine Learning Server using setup.
109
+
Follow the steps to bind SQL Server to Microsoft Machine Learning Server using setup.
110
110
111
111
1. In SSMS, run `SELECT @@version` to verify the server meets minimum build requirements.
112
112
@@ -126,7 +126,7 @@ Follow the steps below to bind SQL Server to Microsoft Machine Learning Server u
126
126
WITH RESULT SETS ((PackageName nvarchar(250), PackageVersion nvarchar(max) ))
127
127
```
128
128
129
-
1. Close down SSMS and any other tools having an open connection to SQL Server. Binding overwrites program files. If SQL Server has open sessions, binding will fail with bind error code 6.
129
+
1. Close SSMS and any other tools having an open connection to SQL Server. Binding overwrites program files. If SQL Server has open sessions, binding will fail with bind error code 6.
130
130
131
131
1. Download Microsoft Machine Learning Server onto the computer that has the instance you want to upgrade. We recommend the [latest version](https://docs.microsoft.com/machine-learning-server/install/machine-learning-server-windows-install#download-machine-learning-server-installer).
132
132
@@ -140,7 +140,7 @@ Follow the steps below to bind SQL Server to Microsoft Machine Learning Server u
140
140
141
141
1. On the **Almost there** page, make a note of the installation folder. The default folder is \Program Files\Microsoft\ML Server.
142
142
143
-
If you want to change the installation folder, click**Advanced** to return to the first page of the wizard. However, you must repeat all previous selections.
143
+
If you want to change the installation folder, select**Advanced** to return to the first page of the wizard. However, you must repeat all previous selections.
144
144
145
145
If upgrade fails, check [SqlBindR error codes](#sqlbindr-error-codes) for more information.
146
146
@@ -154,7 +154,7 @@ The following instructions explain how to place the files for an offline install
154
154
155
155
1. Download the MLSWIN93 Installer. It downloads as a single zipped file. We recommend the [latest version](https://docs.microsoft.com/machine-learning-server/install/machine-learning-server-windows-install#download-machine-learning-server-installer), but you can also install [earlier versions](https://docs.microsoft.com/machine-learning-server/install/r-server-install-windows-offline#download-required-components).
156
156
157
-
1. Download .cab files. The following links are for the 9.3 release. If you require earlier versions, additional links can be found in [R Server 9.1](https://docs.microsoft.com/machine-learning-server/install/r-server-install-windows-offline#download-required-components). Recall that Python/Anaconda can only be added to a SQL Server Machine Learning Services instance. Pre-trained models exist for both Python and R; the .cab provides models in the languages you are using.
157
+
1. Download .cab files. The following links are for the 9.3 release. If you require earlier versions, additional links can be found in [R Server 9.1](https://docs.microsoft.com/machine-learning-server/install/r-server-install-windows-offline#download-required-components). Recall that Python/Anaconda can only be added to a SQL Server Machine Learning Services instance. Pre-trained models exist for both Python and R; the .cab provides models in the languages you're using.
158
158
159
159
| Feature | Download |
160
160
|---------|----------|
@@ -164,7 +164,7 @@ The following instructions explain how to place the files for an offline install
164
164
165
165
1. Transfer .zip and .cab files to the target server.
166
166
167
-
1. On the server, type `%temp%` in the Run command to get the physical location of the temp directory. The physical path varies by machine, but it is usually `C:\Users\<your-user-name>\AppData\Local\Temp`.
167
+
1. On the server, type `%temp%`in the Run command to get the physical location of the temp directory. The physical path varies by machine, but it's usually `C:\Users\<your-user-name>\AppData\Local\Temp`.
168
168
169
169
1. Place the .cab files in the %temp% folder.
170
170
@@ -214,7 +214,7 @@ You have two options for rolling back the binding: re-rerun setup or use SqlBind
214
214
2. The installer identifies local instances that are candidates for unbinding.
215
215
3. Deselect the checkbox next to the instance that you want to revert to the original configuration.
216
216
4. Accept all licensing agreements.
217
-
5. Click**Finish**. The process takes a while.
217
+
5. Select**Finish**. The process takes a while.
218
218
219
219
#### <a name="bkmk_cmdunbind"></a> Unbind using the command line
220
220
@@ -265,7 +265,7 @@ Machine Learning Server Installer and SqlBindR both return the following error c
265
265
|Bind error 0 | Ok (success) | Binding passed with no errors. |
|Bind error 3 | Invalid instance | An instance exists, but is not valid for binding. |
268
+
|Bind error 3 | Invalid instance | An instance exists, but isn't valid for binding. |
269
269
|Bind error 4 | Not bindable | |
270
270
|Bind error 5 | Already bound | You ran the *bind* command, but the specified instance is already bound. |
271
271
|Bind error 6 | Bind failed | An error occurred while unbinding the instance. This error can occur if you run the Machine Learning Server installer without selecting any features. Binding requires that you select both an MSSQL instance and Python and R, assuming the instance is SQL Server 2017. This error also occurs if SqlBindR couldn't write to the Program Files folder. Open sessions or handles to SQL Server will cause this error to occur. If you get this error, reboot the computer and redo the binding steps before starting any new sessions.|
@@ -285,6 +285,17 @@ Later version of SqlBindR automatically restores the original R features, elimin
285
285
286
286
Use R commands to synchronize installed packages to the file system using records in the database. For more information, see [R package management for SQL Server](https://docs.microsoft.com/sql/machine-learning/package-management/install-additional-r-packages-on-sql-server).
287
287
288
+
### Problems with overwritten sqlbinr.ini file in SQL Server
289
+
290
+
Scenario:
291
+
This issue occurs when binding Machine Learning Server 9.4.7 to SQL Server 2017. When Python is updated and bound or when you update to a new CU, it doesn’t understand that Python is bound, and overwrites files. There isn't a known issue with R.
292
+
293
+
As a workaround, create a `sqlbindr.ini` file in the PYTHON_SERVICES directory that isn’t empty. The contents doesn't impact how the file functions.
294
+
295
+
Create a `sqlbindr.ini` file, containing **9.4.7.82**, save to this location:
0 commit comments