Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

When you start an Always On secondary database that has a database snapshot, you encounter non-yielding dump files in Microsoft SQL Server 2019.

Workaround

To work around the problem, you can start SQL Server by using trace flag (TF) 3972, which disables concurrent Page Free Space (PFS) updates feature.

Resolution

Cumulative update information

This problem is fixed in the following cumulative update for SQL Server:

Cumulative Update 14 for SQL Server 2019

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

Latest cumulative update for SQL Server 2019

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 that Microsoft uses to describe software updates.

Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×