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/analytics-platform-system/pdw-firewall-configuration.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,6 @@ The following ports are opened for client connections coming from outside of PDW
40
40
|SQL Server PDW Load Control Flow - Windows Credentials|8002|CTL|
41
41
|_Kerberos|88|AD01 and AD02,|
42
42
|_ldap|389|AD01 and AD02|
43
-
| | | |
44
43
45
44
## Internal Ports
46
45
The following ports are used by PDW for internal communication, but are not opened for connections coming from outside of the PDW appliance.
@@ -54,7 +53,6 @@ The following ports are used by PDW for internal communication, but are not open
54
53
|Failover status (Engine)|15001|CMP|
55
54
|Dynamic (ephemeral) port range|20000-65535|CTL, CMP|
56
55
|SQL Server port ranges (TDS)|1433, 1500-1508|CTL, CMP|
57
-
| | | |
58
56
59
57
> [!NOTE]
60
58
> Creating external tables or external data sources uses TCP port 8020 by default. These statements can be configured to use other ports instead. The Hortonworks JOB_TRACKER_LOCATION default port is 50300. Integrating with other systems and tools may require additional ports.
Copy file name to clipboardExpand all lines: docs/big-data-cluster/big-data-cluster-overview.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,6 @@ Kubernetes is an open source container orchestrator, which can scale container d
118
118
|**Cluster**| A Kubernetes cluster is a set of machines, known as nodes. One node controls the cluster and is designated the master node; the remaining nodes are worker nodes. The Kubernetes master is responsible for distributing work between the workers, and for monitoring the health of the cluster. |
119
119
|**Node**| A node runs containerized applications. It can be either a physical machine or a virtual machine. A Kubernetes cluster can contain a mixture of physical machine and virtual machine nodes. |
120
120
|**Pod**| A pod is the atomic deployment unit of Kubernetes. A pod is a logical group of one or more containers-and associated resources-needed to run an application. Each pod runs on a node; a node can run one or more pods. The Kubernetes master automatically assigns pods to nodes in the cluster. |
121
-
| ||
122
121
123
122
In [!INCLUDE[big-data-cluster](../includes/ssbigdataclusters-ss-nover.md)], Kubernetes is responsible for the state of the cluster. Kubernetes builds and configures the cluster nodes, assigns pods to nodes, and monitors the health of the cluster.
Copy file name to clipboardExpand all lines: docs/big-data-cluster/big-data-options.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,6 @@ This architecture provides the following functionality mapping:
56
56
|Data Pool | Provides data persistence for the cluster. The data pool consists of one or more pods running SQL Server on Linux. It is used to ingest data from SQL queries or Spark jobs.|
57
57
|Storage Pool | The storage pool consists of storage pool pods comprised of SQL Server on Linux, Spark, and HDFS. All the storage nodes in a big data cluster are members of an HDFS cluster.|
58
58
| App Pool | Enables the deployment of applications on a big data cluster by providing interfaces to create, manage, and run applications.|
59
-
|||
60
59
61
60
For more information on these functions, see [Introducing [!INCLUDE[big-data-cluster](../includes/ssbigdataclusters-ss-nover.md)]](big-data-cluster-overview.md).
Starting with **v3.0.0**, the `Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider` supports column encryption key caching capabilities when registering the provider using [SqlConnection.RegisterColumnEncryptionKeyStoreProvidersOnConnection](/dotnet/api/microsoft.data.sqlclient.sqlconnection.registercolumnencryptionkeystoreprovidersonconnection) or [SqlCommand.RegisterColumnEncryptionKeyStoreProvidersOnCommand](/dotnet/api/microsoft.data.sqlclient.sqlcommand.registercolumnencryptionkeystoreprovidersoncommand) APIs.
|[Transparent Network IP Resolution](odbc/using-transparent-network-ip-resolution.md)||[Yes](/dotnet/api/microsoft.data.sqlclient.sqlconnection.connectionstring?view=sqlclient-dotnet-1.1&preserve-view=true)||[Yes](/dotnet/api/system.data.sqlclient.sqlconnection.connectionstring?view=netframework-4.8&preserve-view=true)|
49
-
| | | | | |
50
49
51
50
| <aid="table2"></a>Feature |[ODBC Driver for SQL Server on Windows](odbc/microsoft-odbc-driver-for-sql-server.md)|[ODBC Driver for SQL Server on Linux and macOS](odbc/microsoft-odbc-driver-for-sql-server.md)|[JDBC Driver for SQL Server](jdbc/microsoft-jdbc-driver-for-sql-server.md)|[OLE DB Driver for SQL Server](oledb/oledb-driver-for-sql-server.md)|
52
51
| :-- | :-- | :-- | :-- | :-- |
@@ -66,7 +65,6 @@ We wish all drivers supported every feature and spend effort to ensure feature p
| <aid="table3"></a>Feature |[Drivers for PHP for SQL Server on Windows](php/microsoft-php-driver-for-sql-server.md)<sup>[1](#note1)</sup> |[Drivers for PHP for SQL Server on Linux and macOS](php/microsoft-php-driver-for-sql-server.md)<sup>[1](#note1)</sup> |[Tedious (Node.js)](node-js/node-js-driver-for-sql-server.md)|[pyODBC (Python)](python/pyodbc/python-sql-driver-pyodbc.md)<sup>[1](#note1)</sup> |
72
70
| :-- | :-- | :-- | :-- | :-- |
@@ -86,7 +84,6 @@ We wish all drivers supported every feature and spend effort to ensure feature p
|[Transparent Network IP Resolution](odbc/using-transparent-network-ip-resolution.md)|[Yes](php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md)|[Yes](php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md)||[Yes](odbc/using-transparent-network-ip-resolution.md)|
89
-
| | | | | |
90
87
91
88
<aid="note1"></a><sup>1</sup> Since these drivers rely on the Microsoft ODBC Driver for SQL Server, a version of that driver that supports the feature must also be used.
Copy file name to clipboardExpand all lines: docs/connect/jdbc/overview-of-the-jdbc-driver.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,6 @@ The articles in this section provide a general overview of the JDBC driver, incl
36
36
|[Microsoft JDBC Driver for SQL Server support matrix](microsoft-jdbc-driver-for-sql-server-support-matrix.md)|Support matrix and support lifecycle policy for the Microsoft JDBC driver for SQL Server.|
37
37
|[Frequently asked questions (FAQ) for JDBC driver](frequently-asked-questions-faq-for-jdbc-driver.yml)|Frequently asked questions about the Microsoft JDBC driver.|
38
38
|[Feature dependencies of Microsoft JDBC Driver for SQL Server](feature-dependencies-of-microsoft-jdbc-driver-for-sql-server.md)|Feature dependencies of Microsoft JDBC Driver for SQL Server.|
Copy file name to clipboardExpand all lines: docs/connect/jdbc/reference/jdbc-driver-api-reference.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,6 @@ Documentation for JDBC driver version 6.0, and some later versions, is also here
66
66
|[ISQLServerPreparedStatement](isqlserverpreparedstatement-interface.md)|Represents the basic implementation of JDBC prepared statement functionality.|
67
67
|[ISQLServerResultSet](isqlserverresultset-interface.md)|Represents a JDBC result set.|
68
68
|[ISQLServerStatement](isqlserverstatement-interface.md)|Represents the basic implementation of JDBC statement functionality.|
69
-
| | |
70
69
71
70
## Classes
72
71
@@ -95,7 +94,6 @@ Documentation for JDBC driver version 6.0, and some later versions, is also here
95
94
|[SQLServerXAConnection](sqlserverxaconnection-class.md)|Represents JDBC connections that can participate in distributed (XA) transactions.|
96
95
|[SQLServerXADataSource](sqlserverxadatasource-class.md)|Represents a factory for [SQLServerXAConnection](sqlserverxaconnection-class.md) objects that is used internally.|
97
96
|[SQLServerXAResource](sqlserverxaresource-class.md)|Represents an XAResource for XA distributed transaction management.|
0 commit comments