Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 004b3e4

Browse files
committed
Merge branch 'master' of https://github.com/sudeepku/sql-docs-pr into sql2016-test13-wk
2 parents 7ee834e + 98ee573 commit 004b3e4

1 file changed

Lines changed: 36 additions & 2 deletions

File tree

docs/linux/sql-server-linux-configure-mssql-conf.md

Lines changed: 36 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: This topic describes how to use the mssql-conf tool to configure S
66
author: luisbosquez
77
ms.author: lbosq
88
manager: jhubbard
9-
ms.date: 03/17/2017
9+
ms.date: 03/21/2017
1010
ms.topic: article
1111
ms.prod: sql-linux
1212
ms.technology: database-engine
@@ -32,11 +32,16 @@ ms.custom: H1Hack27Feb2017
3232
- [Default log directory](#datadir): Changes the directory where the new SQL Server database log (.ldf) files are created.
3333
- [Default dump directory](#dumpdir): Change the directory where SQL Server will deposit the memory dumps and other troubleshooting files by default.
3434
- [Default backup directory](#backupdir): Change the directory where SQL Server will send the backup files by default.
35+
- [Mini and full dump prefernces](#coredump): Specify whether to generate both mini dumps and full dumps.
36+
- [Core dump type](#coredump): Choose the type of dump memory dump file to collect.
3537
- [Set traceflags](#traceflags): Set the traceflags that the service is going to use.
3638
- [Set collation](#collation): Set a new collation for SQL Server on Linux.
3739

3840
The following sections show examples of how to use mssql-conf for each of these scenarios.
3941

42+
> [!TIP]
43+
> These examples run mssql-conf by specify the full path: `/opt/mssql/bin/mssql-conf`. If you choose to navigate to that path instead, run mssql-conf in the context of the current directory: `./mssql-conf`.
44+
4045
## <a id="tcpport"></a> Change the TCP port
4146

4247
This option will let you change the TCP port where SQL Server will listen for connections. By default, this port is set to 1433. To change the port, run the following commands:
@@ -129,7 +134,7 @@ To set up this new location, use the following commands:
129134

130135
## <a id="backupdir"></a> Change the default backup directory location
131136

132-
This option will let you change the default location where the backup files are generaqted. By default, these files are generated in /var/opt/mssql/data.
137+
This option will let you change the default location where the backup files are generated. By default, these files are generated in /var/opt/mssql/data.
133138

134139
To set up this new location, use the following commands:
135140

@@ -158,6 +163,35 @@ To set up this new location, use the following commands:
158163
sudo systemctl restart mssql-server
159164
```
160165

166+
## <a id="coredump"></a> Specify core dump settings
167+
168+
If an exception occurs in one of the SQL Server processes, SQL Server creates a memory dump.
169+
170+
There are two options for controlling the type of memory dumps that SQL Server collects: **coredumptype** and **captureminiandfull**. These relate to the two phases of core dump capture.
171+
172+
The first phase capture is controlled by the **coredumptype** setting, which determines the type of dump file generated during an exception. The second phase is enabled when the **captureminiandfull** setting. If **captureminiandfull** is set to true, the dump file specified by **coredumptype** is generated and a second mini dump is also generated. Setting **captureminiandfull** to false disables the second capture attempt.
173+
174+
1. Decide whether to capture both mini and full dumps with the **captureminiandfull** setting.
175+
176+
```bash
177+
sudo /opt/mssql/bin/mssql-conf set captureminiandfull <true or false>
178+
```
179+
180+
2. Specify the type of dump file with the **coredumptype** setting.
181+
182+
```bash
183+
sudo /opt/mssql/bin/mssql-conf set coredumptype <dump type>
184+
```
185+
186+
The following table lists the possible **coredumptype** values.
187+
188+
| Type | Description |
189+
|-----|-----|
190+
| **mini** | Mini is the smallest dump file type. It uses the Linux system information to determine threads and modules in the process. The dump contains only the Host Environment thread stacks and modules. It does not contain indirect memory references or globals. |
191+
| **miniplus** | MiniPlus is similar to mini, but it includes additional memory. It understands the internals of SQLPAL and the host environment, adding the following memory regions to the dump:</br></br> - Various globals</br> - All memory above 64TB</br> - All named regions found in **/proc/$pid/maps**</br> - Indirect memory from threads and stacks</br> - Thread information</br> - Associated Teb’s and Peb’s</br> - Module Information</br> - VMM and VAD tree |
192+
| **filtered** | Filtered uses a subtraction-based design where all memory in the process is included unless specifically excluded. The design understands the internals of SQLPAL and the host environment, excluding certain regions from the dump.
193+
| **full** | Full is a complete process dump that includes all regions located in **/proc/$pid/maps**. This is not controlled by **captureminiandfull** setting. |
194+
161195
## <a id="traceflags"></a> Enable/Disable traceflags
162196

163197
This option will let you enable or disable traceflags for the startup of the SQL Server service. To enable/disable a traceflag use the following commands:

0 commit comments

Comments
 (0)