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/big-data-cluster/concept-security.md
+1-26Lines changed: 1 addition & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,29 +55,6 @@ Username for accessing the HDFS/Spark endpoint:
55
55
56
56
Password for accessing the HDFS/Spark endpoint:
57
57
+ KNOX_PASSWORD=<knox_password>
58
-
59
-
### Update HDFS/Spark (Knox) and Controller passwords
60
-
In order to update Knox and controller admin passwords, the following command can be used:
61
-
62
-
```bash
63
-
mssqlctl set-password service [-h] [-v] servicename clustername
64
-
```
65
-
66
-
Service name indicated which service to update the password for. This can be either "knox" or "controller"
67
-
68
-
69
-
Optional arguments:
70
-
* -h, --help show this help message and exit
71
-
* -v, --verbose Increase output verbosity
72
-
73
-
For example, to update the Knox password for a cluster called "testcluster", run the following:
74
-
75
-
```bash
76
-
export KNOX_PASSWORD = <password>
77
-
mssqlctl set-password service knox testcluster
78
-
```
79
-
80
-
It is currently not possible to change the Knox user name.
81
58
82
59
## Intra cluster authentication
83
60
@@ -93,6 +70,4 @@ Please note that in CTP2.0, only basic authentication is supported. Fine-grained
93
70
94
71
Communication with non-SQL services within the Big Data Cluster, like for example Livy to Spark or Spark to Storage Pool, is secured using certificates. All SQL Sever to SQL Server communication is secured using SQL logins.
Copy file name to clipboardExpand all lines: docs/big-data-cluster/ml-on-master.md
+25-3Lines changed: 25 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: Machine Language services on the master instance of SQL Server Big Data Cluster | Microsoft Docs
3
3
description:
4
-
author: rothja
5
-
ms.author: jroth
4
+
author: NelGson
5
+
ms.author: ms.author:negust
6
6
manager: craigg
7
7
ms.date: 08/27/2018
8
8
ms.topic: conceptual
@@ -11,7 +11,29 @@ ms.prod: sql
11
11
12
12
# Machine Language services on the master instance of SQL Server Big Data Cluster
13
13
14
-
TBD
14
+
SQL Server Machine Learning Services is an add-on feature to the database engine, used for executing R and Python code in SQL Server. This feature is based on the SQL Server extensibility framework, which isolates external processes from core engine processes, but fully integrates with the relational data as stored procedures, as T-SQL script containing R or Python statements, or as R or Python code containing T-SQL.
15
+
16
+
As part of SQL Server Big Data Cluster, this feature will be available from the Master Instance by default. This means that once external script execution is enabled on the Master Instance, it is going to be possible to execute R and Python scripts using sp_execute_external_script.
17
+
18
+
To read more about SQL Server Machine Learning Services, please visit the existing documentation on the topic here. TODO: LINK
19
+
20
+
## Advantages of Machine Learning Services in Big Data Cluster
21
+
22
+
SQL Server 2019 makes it easy for big data sets to be joined to the dimensional and fact data (high value data) typically stored in the enterprise database. The value of the big data greatly increases when it is not just in the hands of parts of an organization, but is also included in reports, dashboards, and applications. At the same time, the data scientists can continue to use the Spark/HDFS ecosystem tools and have easy, real time access to the high-value data in SQL Server.
23
+
With SQL Server 2019 Big Data Clusters, existing customers can do more with their enterprise data lakes. SQL developers and analysts can:
24
+
25
+
* Build applications consuming enterprise data lakes.
26
+
* Reason over all data with Transact-SQL queries.
27
+
* Use the existing ecosystem of SQL Server tools and applications to access and analyze enterprise data.
28
+
* Reduce the need for data movement through data virtualization and data marts in HDFS.
0 commit comments