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

Consider the following scenario:

  • You enable the database mirroring solution for a database in Microsoft SQL Server 2008 R2.

  • You change the file growth settings of the database.

  • Failover occurs from the primary database to the secondary database.


In this scenario, the metadata of the file growth settings is updated incorrectly in the sys.master_files catalog view in the secondary database. This may cause the size of the database file to grow unexpectedly.

Note You expect the file growth settings in both sys.database_files and sys.master_files catalog views to be updated accordingly.

Resolution

Cumulative update information

Cumulative Update 8 for SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

2871401 Cumulative update package 8 for 2008 R2 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative Update 13 for SQL Server 2008 R2 Service Pack 1 (SP1)

The fix for this issue was first released in Cumulative Update 13 for SQL Server 2008 R2 Service Pack 1 (SP1).

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.

For more information, see The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released.

Status

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

References

For more information, see the standard terminology Microsoft uses to describe software updates.

Need more help?

Want more options?

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.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×