Skip to content

Commit 678ea30

Browse files
authored
Merge pull request #4851 from HaiyingYu/revert-4829
Remove the new section. The CU introduced in this section is not released. Will add it back once the new version is released.
2 parents df21d8e + c5789a5 commit 678ea30

1 file changed

Lines changed: 1 addition & 30 deletions

File tree

support/sql/tools/use-sqldumper-generate-dump-file.md

Lines changed: 1 addition & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -205,12 +205,11 @@ When capturing a SQL Server process dump file (especially a filtered dump file o
205205
206206
## Product improvements to reduce the impact on SQL Server
207207
208-
Four major improvements have been added to recent versions of SQL Server to reduce the size of the dump file and/or time for generating the memory dump:
208+
Three major improvements have been added to recent versions of SQL Server to reduce the size of the dump file and/or time for generating the memory dump:
209209
210210
- [Bitmap filtering mechanism](#bitmap-filtering-mechanism)
211211
- [Elimination of repeated dumps on the same issue](#elimination-of-repeated-dumps-on-the-same-issue)
212212
- [Shortened output in the error log](#shortened-output-in-the-error-log)
213-
- [Parallel compression of memory dumps](#parallel-compression-of-memory-dumps)
214213
215214
#### Bitmap filtering mechanism
216215
@@ -252,34 +251,6 @@ External dump process returned no errors.
252251

253252
Previously SQL Server would print information for each session/thread when a manual dump was triggered by the user for example.
254253

255-
#### Parallel compression of memory dumps
256-
257-
To generate dumps faster and make them smaller in size, a compressed memory dump feature was introduced in SQL Server 2022 CU8 and SQL 2019 CU23. When activated, Sqldumper.exe creates multiple threads to read a process's memory simultaneously, compresses it, and then saves it to the dump file. This multi-thread, parallel compression reduces file size and speeds up the dumping process when used with full and filtered dumps.
258-
259-
You can turn on trace flag 2610 to enable compressed memory dump:
260-
261-
```sql
262-
DBCC TRACEON (2610,-1)
263-
GO
264-
DBCC STACKDUMP with FILTERED_DUMP
265-
GO
266-
DBCC TRACEOFF (2610,-1)
267-
```
268-
269-
Alternatively, you can add `-T2610` as a startup parameter to your SQL Server instance so it always creates compressed memory dumps.
270-
271-
If you manually run Sqldumper.exe, you can use the `-zdmp` parameter to capture a compressed memory dump. For example:
272-
273-
```cmd
274-
Sqldumper.exe <ProcessID> 0 0x8100 0 d:\temp -zdmp
275-
```
276-
277-
You can also limit how many cores Sqldumper.exe can use to create the compressed dump by using the `-cpu:X` parameter, where _X_ is the number of CPUs. This parameter is only available when you manually run Sqldumper.exe from the command line:
278-
279-
```cmd
280-
Sqldumper.exe <ProcessID> 0 0x8100 0 d:\temp -zdmp -cpu:8
281-
```
282-
283254
## Factors that prevent or delay creation of memory dumps
284255

285256
The following factors are known to cause delays or prevent the creation of memory dumps.

0 commit comments

Comments
 (0)