使用 Microsoft 登入
登入或建立帳戶。
您好:
選取其他帳戶。
您有多個帳戶
選擇您要用來登入的帳戶。
英文
很抱歉,此文章目前沒有您所使用語言的版本。

Symptoms

Assume that you use In-Memory OLTP in Microsoft SQL Server 2016. You try to recover to the last successful checkpoint, for example during database startup.

If a checksum mismatch with the In-Memory OLTP checkpoint files is detected, the recovery operation fails. However, SQL Server does not log the corruption information that has a severity level of 21 in the error logs, as expected.

Resolution

This fix is included in Service Pack 1 for SQL Server 2016. If a checksum mismatch is detected during database recovery, error 3414 is written to the SQL Server error log and is assigned a severity level of 21.

Each new build for SQL Server 2016 contains all the hotfixes and all the security fixes that were included with the previous build. We recommend that you install the latest build for SQL Server 2016.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

需要更多協助嗎?

想要其他選項嗎?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

這項資訊有幫助嗎?

以下何者是您會在意的事項?
按下 [提交] 後,您的意見反應將用來改善 Microsoft 產品與服務。 您的 IT 管理員將能夠收集這些資料。 隱私權聲明。

感謝您的意見反應!

×