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
1. Open [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. If it is not already installed, you can re-run the SQL Server setup wizard to open a download link and install it.
100
+
1. Open [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. If it is not already installed, you can run the SQL Server setup wizard again to open a download link and install it.
101
101
102
102
2. Connect to the instance where you installed Machine Learning Services, and run the following command:
103
103
@@ -107,13 +107,14 @@ To perform an unattended installation, use the command-line options for SQL Serv
107
107
108
108
The value for the property, `external scripts enabled`, should be **0** at this point. That is because the feature is turned off by default, to reduce the surface area. The feature must be explicitly enabled by an administrator before you can run R or Python scripts.
109
109
110
-
3. To enable the external scripting feature that supports Python, run the following statement. This is exactly the same process that is used to enable R, because the underlying extensibility feature supports both languages.
110
+
3. To enable the external scripting feature that supports Python, run the following statement.
111
111
112
112
```SQL
113
113
EXEC sp_configure 'external scripts enabled', 1
114
114
RECONFIGURE WITH OVERRIDE
115
115
```
116
-
116
+
This is exactly the same process that is used to enable R, because the underlying extensibility feature supports both languages.
117
+
117
118
4. Restart the SQL Server service for the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance. Restarting the SQL Server service will also automatically restart the related [!INCLUDE[rsql_launchpad](../../includes/rsql-launchpad-md.md)] service.
118
119
119
120
You can restart the service using the **Services** panel in Control Panel, or by using [SQL Server Configuration Manager](../../relational-databases/sql-server-configuration-manager.md).
@@ -155,20 +156,20 @@ If this command was successful, you can run Python commands from SQL Server Mana
155
156
156
157
If not, review the following list and see if changes to the configuration of the service or database might be needed.
157
158
158
-
It is important to note that not all of the listed changes are required, and none might be required. It depends on your security schema, where you installed SQL Server, and how you expect users to connect to the database and run external scripts.
159
+
It is important to note that not all the listed changes are required, and none might be required. It depends on your security schema, where you installed SQL Server, and how you expect users to connect to the database and run external scripts.
159
160
160
161
### <a name="bkmk_configureAccounts"></a> Enable implied authentication for Launchpad account group
161
162
162
163
During setup, a number of new Windows user accounts are created for the purpose of running tasks under the security token of the [!INCLUDE[rsql_launchpad_md](../../includes/rsql-launchpad-md.md)] service. When a user sends a Python or R script from an external client, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] will activate an available worker account, map it to the identity of the calling user, and run the script on behalf of the user.
163
164
164
-
This is called called *implied authentication*, and is a service of the database engine that supports secure execution of external scripts in SQL Server 2016and SQL Server 2017.
165
+
This is called *implied authentication*, and is a service of the database engine that supports secure execution of external scripts in SQL Server 2016and SQL Server 2017.
165
166
166
-
You can view these accounts in the Windows user group, **SQLRUserGroup**. By default, 20 worker accounts are created, which is typically more than enough for running external script jobs.
167
+
You can view these accounts in the Windows user group, **SQLRUserGroup**. By default, 20 worker accounts are created, which is usually more than enough for running external script jobs.
167
168
168
169
> [!IMPORTANT]
169
170
> The worker group is named SQLRUserGroup regardless of the type of script you are running. There is a single group for each instance.
170
171
171
-
If you need to run R scripts from a remote data science client and are using Windows authentication, these worker accounts must be given permission to log into the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance on your behalf.
172
+
If you need to run R scripts from a remote data science client and are using Windows authentication, these worker accounts must be given permission to log in to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance on your behalf.
172
173
173
174
1. In [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], in Object Explorer, expand **Security**, right-click **Logins**, andselect**New Login**.
174
175
2. In the **Login - New** dialog box, click **Search**.
@@ -183,17 +184,18 @@ If you need to run R scripts from a remote data science client and are using Win
183
184
184
185
### Give users permission to run external scripts
185
186
186
-
If you installed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] yourself and are running Python scripts in your own instance, you are typically executing scripts as an administrator and thus have implicit permission over various operations and all data in the database.
187
+
If you installed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] yourself and are running Python scripts in your own instance, you typically execute scripts as an administrator, and thus have implicit permission over various operations and all data in the database.
187
188
188
-
However, in an enterprise scenario, most users, including those accessing the database using SQL logins, do not have such elevated permissions. Therefore, for each user that will be running external scripts, you must grant users of machine learning services the permission to run scripts in each database where Python will be used.
189
+
However, in an enterprise scenario, most users, including those accessing the database using SQL logins, do not have such elevated permissions. Therefore, for each user who will be using Python, you must grant users of machine learning services the permission to run external scripts in each database where Python will be used.
189
190
190
191
```SQL
191
192
USE <database_name>
192
193
GO
193
194
GRANT EXECUTE ANY EXTERNAL SCRIPT TO [UserName]
194
195
```
195
196
196
-
Note that permissions are not specific to the supported script language. In other words, there are not separate permission levels for R script vs. Python script. If you need to maintain separate permissions for these languages, you can install R and Python on separate instances.
197
+
> [!NOTE]
198
+
> Permissions are not specific to the supported script language. In other words, there are not separate permission levels for R script vs. Python script. If you need to maintain separate permissions for these languages, you can install R and Python on separate instances.
0 commit comments