Hotfix and Security Content Publishing: 98046

徵狀

假設您有 SQL Server 2017年,Linux 安裝上。當您使用 DBCC STACKDUMP 命令產生的 SQLDUMPER。EXE 啟始傾印從SQL Server 2017年的累積的更新 9 (CU 9)開始,累積更新 13 (CU 13 個) 的 SQL Server 2017,您可能會注意到它無法運作。

狀態

Microsoft 已確認<適用於>一節所列的 Microsoft 產品確實有上述問題。

解決方案

在 SQL Server 的下列累積更新程式修正這個問題:

有關 SQL Server 所累積的更新:

SQL Server 的每個新的累積更新包含的所有修補程序與安全性修正,全都包含在先前的累積更新。检验 SQL Server 的最新的累積更新︰

其他相關資訊

如需詳細資訊,請參閱如何使用 DBCC STACKDUMP

參考

深入了解 術語,Microsoft 會使用描述軟體更新。

Call Stack Information

Call Site
sqlmin!CStackDumpAccess::{ctor}
sqlmin!CStackDumpAutoInit::{ctor}
sqlmin!UtilDbccStackDump+0x274
sqlmin!DbccStackDump+0x38a
sqllang!DbccCommand::Execute+0x1af
sqllang!CStmtDbcc::XretExecute+0x89a
sqllang!CExecStmtLoopVars::ExecuteXStmtAndSetXretReturn+0xf
sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x4c5
sqllang!CMsqlExecContext::FExecute+0xaae
sqllang!CSQLSource::Execute+0xa2c
sqllang!process_request+0xe52
sqllang!process_commands_internal+0x289
sqllang!process_messages+0x213
sqldk!SOS_Task::Param::Execute+0x231
sqldk!SOS_Scheduler::RunTask+0xad
sqldk!SOS_Scheduler::ProcessTasks+0x3cd
sqldk!SchedulerManager::WorkerEntryPoint+0x2a1
sqldk!SystemThread::RunWorker+0x8f
sqldk!SystemThreadDispatcher::ProcessWorker+0x2e7
sqldk!SchedulerManager::ThreadEntryPoint+0x1d8
KERNEL32!BaseThreadInitThunk+0x14
ntdll!RtlUserThreadStart+0x21
0x00007fc9`1e4fa000

SqlDumper!CMiniDumper::ParseParameters
SqlDumper!CMiniDumper::Init+0x17
SqlDumper!SQLDumperMain+0xe8
SqlDumper!SQLDumperSEHWrapper+0x12
SqlDumper!__tmainCRTStartup+0x10f
sqlpal!NtpProcessStartThunk+0xef
KERNEL32_7806e0000!BaseThreadInitThunk+0x14
ntdll_780230000!RtlUserThreadStart+0x21
0x00007fc9`1ed08800

Bug Information:

KE: cobibi
Author: 
Writer: v-madora
Tech reviewer: tejasaks; pradm; bobward; sureshka; jaynar; greynya; adis; keiikoga; cobibi
Editor: v-jizho

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

How satisfied are you with the translation quality?
What affected your experience?

Thank you for your feedback!

×