Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link: http://hub-nl.insight.com/i/692679

Contents of this Issue

Navigation

Page 125 of 212

113 C H A P T E R 6 | More analytics Server configuration R Services is available in the Standard, Developer, and Enterprise editions of SQL Server 2016 or in Express Edition with Advanced Services. Only the Enterprise edition supports execution of R packages in a high-performance, parallel architecture. In the server environment, you install one of the following components from the SQL Server installation media: R Services (In-Database) A database-engine feature that configures the database service to use R jobs and installs extensions to support external scripts and processes. It also downloads Microsoft R Open (MRO), an open-source R distribution. This feature requires you to have a default or named instance of SQL Server 2016. R Services (Standalone) A standalone component that does not require a database-engine instance and is available only in the Enterprise edition of SQL Server 2016. It includes enhanced R packages and connectivity tools from Revolution Analytics and open-source R tools and base packages. Selection of this component also downloads and installs MRO. After installation of R Services (In-Database), you must execute the following command to enable R Services and then restart the SQL Server service: exec sp_configure 'external scripts enabled', 1 reconfigure with override As part of the installation of R Services (In-Database), 20 new Windows user accounts are added to the server as members of a new Windows group, SQLRUserGroup. This group is used to run tasks using the security token of the new SQL Server Trusted Launchpad service. Using implied authentication, SQL Server activates one of these accounts when you send an R script from a remote client, maps it to your identity, and runs the script on your behalf. If you need to run R scripts from a remote client using Windows authentication instead of a SQL login, you must grant permissions to these accounts to log on to SQL Server on your behalf. To do this, perform the following steps: 1. In Object Explorer in SQL Server Management Studio (SSMS), expand Security, right-click Logins, and select New Login. 2. Click Search in the Login – New dialog box. 3. Click Object Types in the Select User, Service Account, or Group dialog box. 4. Select the Groups check box, clear all other check boxes, and then click OK. 5. In the Enter The Object Name To Select box, type SQLRUserGroup, and then click Check Names. 6. Select the SQLRUserGroup associated with the SQL Server instance, and then click OK twice. For each user that needs to run R scripts on a SQL Server with R Services (In-Database) installed, you must grant the following permissions in each database in which the user needs to use R: USE GO GRANT EXECUTE ANY EXTERNAL SCRIPT TO Note The default memory-allocation settings might allow SQL Server to consume most of the available physical memory without leaving adequate memory for R Services (In-Database). Consider changing the maximum memory for SQL Server to 80 percent of available physical memory. Refer to "Server Memory Server Configuration Options" at https://msdn.microsoft.com/en- us/library/ms178067.aspx for more information about configuring server memory. Client workstation To prepare a client workstation to work with R Services, install the following components:

Articles in this issue

Links on this page

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016