Skip to content

Commit de32367

Browse files
author
MightyPen
committed
markdig fixes for tables, phase 1, before run C# MarkdigDetect_NeededBlankLines2.exe
1 parent ea7e4bd commit de32367

27 files changed

Lines changed: 380 additions & 317 deletions

‎docs/advanced-analytics/install/sql-ml-cab-downloads.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: R and Python CAB and package downloads for SQL Server 2017 Machine
44
ms.prod: sql
55
ms.technology: machine-learning
66

7-
ms.date: 12/18/2018
7+
ms.date: 01/19/2019
88
ms.topic: conceptual
99
author: HeidiSteen
1010
ms.author: heidist
@@ -30,14 +30,14 @@ You can also apply cumulative updates to a standalone server.
3030

3131
CAB files are listed in reverse chronological order. When you download the CAB files and transfer them to the target computer, place them in a convenient folder such as **Downloads** or the setup user's %temp% folder.
3232

33-
Release |Component | Download link | Issues addressed |
34-
---------|----------|----------------|------------------|
33+
|Release |Component | Download link | Issues addressed |
34+
|---------|----------|----------------|------------------|
3535
**[SQL Server 2017 CU13](https://support.microsoft.com/help/4466404)** | | | |
3636
| | Microsoft R Open | [SRO_3.3.3.300_1033.cab](https://go.microsoft.com/fwlink/?LinkId=863894)| No change from previous versions. |
3737
| | R Server |[SRS_9.2.0.1300_1033.cab](https://go.microsoft.com/fwlink/?LinkId=2038263&clcid=1033)| Contains a fix for upgrading an [operationalized standalone R Server](https://docs.microsoft.com/machine-learning-server/what-is-operationalization), as installed through SQL Server Setup. Use the CU13 CABs and follow [these instructions](sql-machine-learning-standalone-windows-install.md#apply-cu) to apply the update. |
3838
| | Microsoft Python Open | [SPO_9.2.0.24_1033.cab](https://go.microsoft.com/fwlink/?LinkId=851502)| No change from previous versions. |
3939
| | Python Server |[SPS_9.2.0.1300_1033.cab](https://go.microsoft.com/fwlink/?LinkId=2038197&clcid=1033)| Contains a fix for upgrading an [operationalized standalone Python Server](https://docs.microsoft.com/machine-learning-server/what-is-operationalization), as installed through SQL Server Setup. Use the CU13 CABs and follow [these instructions](sql-machine-learning-standalone-windows-install.md#apply-cu) to apply the update. |
40-
**[SQL Server 2017 CU10](https://support.microsoft.com/help/4342123)-[CU11](https://support.microsoft.com/help/4462262)-[CU12](https://support.microsoft.com/help/4464082)** | | | |
40+
|**[SQL Server 2017 CU10](https://support.microsoft.com/help/4342123)-[CU11](https://support.microsoft.com/help/4462262)-[CU12](https://support.microsoft.com/help/4464082)** | | | |
4141
| | Microsoft R Open | [SRO_3.3.3.300_1033.cab](https://go.microsoft.com/fwlink/?LinkId=863894)| No change from previous versions. |
4242
| | R Server |[SRS_9.2.0.1000_1033.cab](https://go.microsoft.com/fwlink/?LinkId=2006287&clcid=1033)| Minor fixes.|
4343
| | Microsoft Python Open | [SPO_9.2.0.24_1033.cab](https://go.microsoft.com/fwlink/?LinkId=851502)| No change from previous versions. |

‎docs/advanced-analytics/r/installing-and-managing-r-packages.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: R and Python packages installed by SQL Server for R Services, R Ser
44
ms.prod: sql
55
ms.technology: machine-learning
66

7-
ms.date: 05/29/2018
7+
ms.date: 01/19/2019
88
ms.topic: conceptual
99
author: HeidiSteen
1010
ms.author: heidist
@@ -19,7 +19,7 @@ This article lists the R and Python packages installed with SQL Server and where
1919

2020
R packages are installed with [SQL Server 2016 R Services](../install/sql-r-services-windows-install.md) and [SQL Server 2017 Machine Learning Services](../install/sql-machine-learning-services-windows-install.md) when you select the R feature during setup.
2121

22-
Packages | 2016 | 2017 | Description |
22+
|Packages | 2016 | 2017 | Description |
2323
|----------------|--------------|--------------|-------------|
2424
| [RevoScaleR](https://docs.microsoft.com/r-server/r-reference/revoscaler/revoscaler) | 8.0.3 | 9.2 | Used for remote compute contexts, streaming, parallel execution of rx functions for data import and transformation, modeling, visualization, and analysis. |
2525
| [sqlrutils](https://docs.microsoft.com/machine-learning-server/r-reference/sqlrutils/sqlrutils) | 8.0.3 | 9.2 |Used for including R script in stored procedures. |

‎docs/database-engine/availability-groups/windows/sql-server-always-on-database-health-detection-failover-option.md‎

Lines changed: 33 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Database Health Detection Failover Option | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "04/28/2017"
4+
ms.date: 01/19/2019
55
ms.prod: sql
66
ms.reviewer: ""
77
ms.technology: high-availability
@@ -29,8 +29,8 @@ The availability group database level health detection option is widely recommen
2929

3030
For example, with database level health detection option on, if SQL Server was unable to write to the transaction log file for one of the databases, the status of that database would change to indicate failure, and the availability group would soon fail over, and your application could reconnect and continue working with minimal interruption once the databases are online again.
3131

32-
Enabling database level health detection
33-
----
32+
### Enabling database level health detection
33+
3434
Though it is generally recommended, the Database Health option is **off by default**, in effort to keep backward compatibility with the default settings in prior versions.
3535

3636
There are several easy ways to enable database level health detection setting:
@@ -46,7 +46,7 @@ There are several easy ways to enable database level health detection setting:
4646

4747
3. Transact-SQL Syntax to **CREATE AVAILABILITY GROUP**. The DB_FAILOVER parameter accepts values ON or OFF.
4848

49-
```Transact-SQL
49+
```sql
5050
CREATE AVAILABILITY GROUP [Contoso-ag]
5151
WITH (DB_FAILOVER=ON)
5252
FOR DATABASE [AutoHa-Sample]
@@ -59,7 +59,7 @@ There are several easy ways to enable database level health detection setting:
5959

6060
4. Transact-SQL Syntax to **ALTER AVAILABILITY GROUP**. The DB_FAILOVER parameter accepts values ON or OFF.
6161

62-
```Transact-SQL
62+
```sql
6363
ALTER AVAILABILITY GROUP [Contoso-ag] SET (DB_FAILOVER = ON);
6464
6565
ALTER AVAILABILITY GROUP [Contoso-ag] SET (DB_FAILOVER = OFF);
@@ -83,16 +83,16 @@ Database level health detection implements a flexible failover policy which conf
8383

8484
The system DMV sys.availability_groups shows a column db_failover which indicates if the database level health detection option is off (0) or on (1).
8585

86-
```Transact-SQL
86+
```sql
8787
select name, db_failover from sys.availability_groups
8888
```
8989

9090

9191
Example dmv output:
9292

93-
name | db_failover
94-
---------|---------
95-
| Contoso-ag | 1 |
93+
|name | db_failover|
94+
|---------|---------|
95+
| Contoso-ag | 1 |
9696

9797
### ErrorLog
9898
The SQL Server Errorlog (or text from sp_readerrorlog) will show the error message 41653 when an availability group has failed over, due to the database level health detection checks.
@@ -129,7 +129,8 @@ This XEvent is triggered on the primary replica only. This XEvent is triggered w
129129
Here is a example to create an XEvent session that captures this event. As no path is specified, the XEvent output file should be located in the default SQL Server error log path. Execute this on the primary replica of your availability group:
130130

131131
Example Extended Event Session Script
132-
```
132+
133+
```sql
133134
CREATE EVENT SESSION [AlwaysOn_dbfault] ON SERVER
134135
ADD EVENT sqlserver.availability_replica_database_fault_reporting
135136
ADD TARGET package0.event_file(SET filename=N'dbfault.xel',max_file_size=(5),max_rollover_files=(4))
@@ -145,32 +146,32 @@ Using SQL Server Management Studio, connect to the primary SQL Server, and expan
145146

146147
Explanation of the fields:
147148

148-
|Column Data | Description
149-
|---------|---------
150-
|availability_group_id |The ID of the availability group.
151-
|availability_group_name |The name of the availability group.
152-
|availability_replica_id |The ID of the availability replica.
153-
|availability_replica_name |The name of the availability replica.
154-
|database_name |The name of the database reporting the fault.
155-
|database_replica_id |The ID of the availability replica database.
156-
|failover_ready_replicas |The number of automatic failover secondary replicas that are synchronized.
157-
|fault_type | The fault id reported. Possible values: <br/> 0 - NONE <br/>1 - Unknown<br/>2 - Shutdown
158-
|is_critical | This value should always return true for the XEvent as of SQL Server 2016.
149+
|Column Data | Description|
150+
|---------|---------|
151+
|availability_group_id |The ID of the availability group.|
152+
|availability_group_name |The name of the availability group.|
153+
|availability_replica_id |The ID of the availability replica.|
154+
|availability_replica_name |The name of the availability replica.|
155+
|database_name |The name of the database reporting the fault.|
156+
|database_replica_id |The ID of the availability replica database.|
157+
|failover_ready_replicas |The number of automatic failover secondary replicas that are synchronized.|
158+
|fault_type | The fault id reported. Possible values: <br/> 0 - NONE <br/>1 - Unknown<br/>2 - Shutdown|
159+
|is_critical | This value should always return true for the XEvent as of SQL Server 2016.|
159160

160161

161162
In this example output, the fault_type shows that a critical event happened on the availability group Contoso-ag, on replica named SQLSERVER-1, due to database name AutoHa-Sample2, with fault type 2- Shutdown.
162163

163-
|Field | Value
164-
|---------|---------
165-
|availability_group_id | 24E6FE58-5EE8-4C4E-9746-491CFBB208C1
166-
|availability_group_name | Contoso-ag
167-
|availability_replica_id | 3EAE74D1-A22F-4D9F-8E9A-DEFF99B1F4D1
168-
|availability_replica_name | SQLSERVER-1
169-
|database_name | AutoHa-Sample2
170-
|database_replica_id | 39971379-8161-4607-82E7-098590E5AE00
171-
|failover_ready_replicas | 1
172-
|fault_type | 2
173-
|is_critical | True
164+
|Field | Value|
165+
|---------|---------|
166+
|availability_group_id | 24E6FE58-5EE8-4C4E-9746-491CFBB208C1|
167+
|availability_group_name | Contoso-ag|
168+
|availability_replica_id | 3EAE74D1-A22F-4D9F-8E9A-DEFF99B1F4D1|
169+
|availability_replica_name | SQLSERVER-1|
170+
|database_name | AutoHa-Sample2|
171+
|database_replica_id | 39971379-8161-4607-82E7-098590E5AE00|
172+
|failover_ready_replicas | 1|
173+
|fault_type | 2|
174+
|is_critical | True|
174175

175176

176177
### Related References

‎docs/database-engine/configure-windows/default-sql-server-network-protocol-configuration.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Default SQL Server Network Protocol Configuration | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "07/11/2017"
4+
ms.date: 01/19/2019
55
ms.prod: sql
66
ms.prod_service: high-availability
77
ms.reviewer: ""
@@ -26,16 +26,16 @@ Use the [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] Network Con
2626

2727
The following table describes the configuration after installation.
2828

29-
Edition | New installation vs. previous installation is present | Shared memory | TCP/IP | Named pipes
29+
|Edition | New installation vs. previous installation is present | Shared memory | TCP/IP | Named pipes|
3030
| -------- | -- | -- | -- | -- |
31-
Enterprise | New installation | Enabled | Enabled | Disabled for network connections.
32-
Standard | New installation | Enabled | Enabled | Disabled for network connections.
33-
Web | New installation | Enabled | Enabled | Disabled for network connections.
34-
Developer | New installation | Enabled | Disabled | Disabled for network connections.
35-
Evaluation | New installation | Enabled | Enabled | Disabled for network connections.
36-
SQL Server Express | New installation | Enabled | Disabled | Disabled for network connections.
37-
All editions | Previous installation is present but is not being upgraded. | Same as new installation | Same as new installation | Same as new installation
38-
All editions | Upgrade | Enabled | Settings from the previous installation are preserved. | Settings from the previous installation are preserved.
31+
|Enterprise | New installation | Enabled | Enabled | Disabled for network connections.|
32+
|Standard | New installation | Enabled | Enabled | Disabled for network connections.|
33+
|Web | New installation | Enabled | Enabled | Disabled for network connections.|
34+
|Developer | New installation | Enabled | Disabled | Disabled for network connections.|
35+
|Evaluation | New installation | Enabled | Enabled | Disabled for network connections.|
36+
|SQL Server Express | New installation | Enabled | Disabled | Disabled for network connections.|
37+
|All editions | Previous installation is present but is not being upgraded. | Same as new installation | Same as new installation | Same as new installation|
38+
|All editions | Upgrade | Enabled | Settings from the previous installation are preserved. | Settings from the previous installation are preserved.|
3939

4040

4141
>[!NOTE]

‎docs/integration-services/scale-out/integration-services-ssis-scale-out-master.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "SQL Server Integration Services (SSIS) Scale Out Master | Microsoft Docs"
33
description: "This article describes the Scale Out Master component of SSIS Scale Out"
44
ms.custom: performance
5-
ms.date: "12/19/2017"
5+
ms.date: 01/19/2019
66
ms.prod: sql
77
ms.prod_service: "integration-services"
88
ms.reviewer: ""
@@ -40,15 +40,15 @@ The Scale Out Master service is a Windows service that is responsible for the co
4040
You configure the Scale Out Master service by using the `\<drive\>:\Program Files\Microsoft SQL Server\140\DTS\Binn\MasterSettings.config` file. You have to restart the service after updating the configuration file.
4141

4242

43-
Configuration |Description |Default Value
44-
---------|---------|---------
45-
PortNumber|The network port number used to communicate with a Scale Out Worker.|8391
46-
SSLCertThumbprint|The thumbprint of the SSL certificate used to protect the communication with a Scale Out Worker.|The thumbprint of the SSL certificate specified during the Scale Out Master installation
47-
SqlServerName|The name of the [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] that contains the SSISDB catalog. For example, ServerName\\\\InstanceName.|The name of the SQL Server that is installed with the Scale Out Master.
48-
CleanupCompletedJobsIntervalInMs|The interval for cleaning up completed execution jobs, in milliseconds.|43200000
49-
DealWithExpiredTasksIntervalInMs|The interval for dealing with expired execution jobs, in milliseconds.|300000
50-
MasterHeartbeatIntervalInMs|The interval for the Scale Out Master heartbeat, in milliseconds. This property specifies the interval at which Scale Out Master updates its online status in the SSISDB catalog.|30000
51-
SqlConnectionTimeoutInSecs|The SQL connection timeout in seconds when connecting to SSISDB.|15
43+
|Configuration |Description |Default Value |
44+
---------|---------|---------|
45+
|PortNumber|The network port number used to communicate with a Scale Out Worker.|8391|
46+
|SSLCertThumbprint|The thumbprint of the SSL certificate used to protect the communication with a Scale Out Worker.|The thumbprint of the SSL certificate specified during the Scale Out Master installation|
47+
|SqlServerName|The name of the [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] that contains the SSISDB catalog. For example, ServerName\\\\InstanceName.|The name of the SQL Server that is installed with the Scale Out Master.|
48+
|CleanupCompletedJobsIntervalInMs|The interval for cleaning up completed execution jobs, in milliseconds.|43200000|
49+
|DealWithExpiredTasksIntervalInMs|The interval for dealing with expired execution jobs, in milliseconds.|300000|
50+
|MasterHeartbeatIntervalInMs|The interval for the Scale Out Master heartbeat, in milliseconds. This property specifies the interval at which Scale Out Master updates its online status in the SSISDB catalog.|30000|
51+
|SqlConnectionTimeoutInSecs|The SQL connection timeout in seconds when connecting to SSISDB.|15|
5252
||||
5353

5454
## View the Scale Out Master service log

0 commit comments

Comments
 (0)