Skip to content

Commit 80dc669

Browse files
committed
Acrolinx fixes
1 parent fb2b770 commit 80dc669

1 file changed

Lines changed: 13 additions & 13 deletions

File tree

docs/advanced-analytics/r/install-additional-r-packages-on-sql-server.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -59,13 +59,13 @@ This article describes how to install new R packages to an instance of SQL Serve
5959

6060
## Install new packages
6161

62-
This section provide detailed procedures for the following key package installation scenarios. The best method for you to use depends on these factores:
62+
This section provide detailed procedures for key package installation scenarios. Choose the best method, depending on:
6363

6464
- The version of SQL Server you are using
6565

66-
- Whether you are the sole owner of the instance, or are trying to mamaneg packages for multiple people using database roles.
66+
- Whether you are the sole owner of the instance, or are trying to manage packages for multiple people using database roles.
6767

68-
- Whether you are installing one packages, or multiple packages with dependencies
68+
- Whether you are installing one package, or multiple packages with dependencies
6969

7070
**Use SQL Server package management**
7171

@@ -83,7 +83,7 @@ If your instance supports package management features, you can use either T-SQL
8383

8484
[Install multiple packages from a miniCRAN repository](#bkmk_minicran)
8585

86-
**Use conventional R rools**
86+
**Use conventional R tools**
8787

8888
If you are using an earlier version of SQL Server R services, follow these instructions to install packages using conventional R tools. Optionally, use miniCRAN to prepare a collection of packages for installation.
8989

@@ -103,15 +103,15 @@ If you are using an earlier version of SQL Server R services, follow these instr
103103

104104
2. Connect to the server using an account that has permissions to install new packages, using one of the supported database roles described in this topic: [R package management for SQL Server](r-package-management-for-sql-server-r-services.md)
105105

106-
3. Copy the zipped file containing the R package you want to install to a folder on the server computer, such as your **Users** or **Documents** folder. You cannot add a package from a networked drive or from a folder on the client computer. If you have used miniCRAN to create a package repository, copy the package repository in its entirety to any local folder on the server: i.e., not on a networked drive.
106+
3. Copy the zipped file containing the R package you want to install to a folder on the server computer, such as your **Users** or **Documents** folder. You cannot add a package from a networked drive or from a folder on the client computer. If you have used miniCRAN to create a package repository, copy the package repository in its entirety to any local folder on the server: that is, not on a networked drive.
107107

108108
If you don't have access to any folders on the server, you can pass the package contents in binary format. See [CREATE EXTERNAL LIBRARY](https://docs.microsoft.com/sql/t-sql/statements/create-external-library-transact-sql) for an example.
109109

110110
4. From the database where you want to use the package, run the [CREATE EXTERNAL
111111
LIBRARY](https://docs.microsoft.com/sql/t-sql/statements/create-external-library-transact-sql)
112112
statement.
113113

114-
For this example, we'll assume that your account has permission to upload new packages to the server and install them to shared scope in the database.
114+
For this example, we assume that your account has permission to upload new packages to the server and install them to **shared** scope in the database.
115115

116116
The following statement adds the release version of the [zoo](https://cran.r-project.org/web/packages/zoo/index.html) package into the current database context, from a local fileshare.
117117

@@ -135,7 +135,7 @@ If you are using an earlier version of SQL Server R services, follow these instr
135135
library(zoo)'
136136
```
137137

138-
If successful, the **Messages** window should report a message such as "package 'zoo' successfully unpacked and MD5 sums checked". If a required package is already installed, the installation process will attach and load the required package.
138+
If successful, the **Messages** window should report a message such as "package 'zoo' successfully unpacked and MD5 sums checked." If a required package is already installed, the installation process then attaches and loads the required package.
139139

140140
> [!NOTE]
141141
> If a required package is not available, an error is returned: "there is no package called \<required_package\>".
@@ -218,7 +218,7 @@ You can use R tools to install new packages on both SQL Server 2016 and SQL Serv
218218

219219
When asked for a mirror site, select any site that is convenient for your location.
220220

221-
If the target package depends on additional packages, the R installer will automatically download the dependencies and install them for you.
221+
If the target package depends on additional packages, the R installer automatically downloads the dependencies and installs them for you.
222222

223223
**Install package manually or on a computer with no Internet access**
224224

@@ -234,7 +234,7 @@ You can use R tools to install new packages on both SQL Server 2016 and SQL Serv
234234

235235
### <a name="bkmk_minicran"></a> Install multiple packages from a miniCRAN repository
236236

237-
If you are installing packages from a miniCRAN repository, the overall process is very similar to installing a package from a single zipped file. However, rather than uploading an individual package in zipped format, the miniCRAN repository contains the target package as well as any related required packages.
237+
The overall process of installing packages from a miniCRAN repository is similar to installing a package from a single zipped file. However, rather than uploading an individual package in zipped format, the miniCRAN repository contains the target package as well as any related required packages.
238238

239239
1. Prepare the miniCRAN repository and then copy the zipped file to a local folder on the server.
240240

@@ -258,19 +258,19 @@ If you are installing packages from a miniCRAN repository, the overall process i
258258
library(randomForest)'
259259
```
260260

261-
If successful, the **Messages** window should report a message such as "package 'randomForest' successfully unpacked and MD5 sums checked" and also "Finished chained execution".
261+
If successful, the **Messages** window should report a message such as "package 'randomForest' successfully unpacked and MD5 sums checked" and "Finished chained execution".
262262

263263
## Package installation tips
264264

265265
This section provides assorted tips and sample code related to R package installation on SQL Server.
266266

267267
### <a name="packageVersion"></a> Get the correct package version and format
268268

269-
There are multiple sources for R packages, the best known among them being CRAN and Bioconductor. The official site for the R language (<https://www.r-project.org/>) lists many of these resources. Many packages are also published to GitHub, where you can obtain the source code. However, you may also have been given R packages that were developed by someone in your company.
269+
There are multiple sources for R packages, the best known among them being CRAN and Bioconductor. The official site for the R language (<https://www.r-project.org/>) lists many of these resources. Many packages are published to GitHub, where you can obtain the source code. However, you may have been given R packages that were developed by someone in your company.
270270

271271
Regardless of the source, you must ensure that the package you want to install has a binary format for the Windows platform. Otherwise the downloaded package cannot run in the SQL Server environment.
272272

273-
You should also determine whether the package is compatible with the version of R that is running in SQL Server.
273+
Before downloading, you should also check whether the package is compatible with the version of R that is running in SQL Server.
274274

275275
### <a name="bkmk_zipPreparation"></a> Download package as zipped file
276276

@@ -288,7 +288,7 @@ For example, the following procedure describes now to get the correct version of
288288

289289
This process creates a local copy of the package. You can then install the package, or copy the zipped package to a server that does not have internet access.
290290

291-
For more information about the contents of the zip file format, and how to create an R package, we recommend this tutorial, which you can download in PDF format from the R project site: [Freidrich Leisch: Creating R Packages](http://cran.r-project.org/doc/contrib/Leisch-CreatingPackages.pdf).
291+
For more information about the contents of the zip file format, and how to create an R package, we recommend this tutorial, which you can download in PDF format from the R project site: [Creating R Packages](http://cran.r-project.org/doc/contrib/Leisch-CreatingPackages.pdf).
292292

293293
### <a name="bkmk_packageDependencies"></a> Get package dependencies
294294

0 commit comments

Comments
 (0)