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.

Microsoft distributes Microsoft SQL Server 2008 and 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 and 2008 R2 fix release.

Symptoms

Consider the following scenario:

  • You create a database in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2. The database has the AUTO_CLOSE database option set to ON.

  • You create a maintenance plan to back up the database, and you select the Ignore databases where the state is not online option.

  • You try to run the maintenance plan. For example, you try to run the maintenance plan by using SQL Server Management Studio or by running a SQL Server Agent job.

  • The maintenance plan runs successfully.

In this scenario, the database is not backed up.

Note This issue also occurs if the database is set to the RESTORING or STANDBYstatus. For example, the principal database is not backed up in a database-mirroring pair if the mirror database is in the RESTORING mode while the principal database is online.

Cause

This issue occurs because the function for the Ignore databases where the state is not online option cannot detect whether a database is online.

Note This issue occurs only if the database is set to the AUTO_CLOSE, STANDBY, or RESTORING status. This issue may occur if the principal database was shut down in a database-mirroring scenario.

Resolution

Cumulative update information

SQL Server 2008 Service Pack 2

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

2498535 Cumulative update package 3 for SQL Server 2008 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 fix release. Microsoft recommends 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:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2


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

2489376 Cumulative Update package 6 for SQL Server 2008 R2 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, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 Service Pack 1

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

2467236 Cumulative update package 12 for SQL Server 2008 Service Pack 1Note 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 fix release. Microsoft recommends 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:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Status

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

More Information

SQL Server Management Studio (SSMS) uses the DatabaseStatus enumeration to map the database state in the sys.databases catalog view. For example, the ONLINE state in sys.databases is mapped to the NORMAL state in SMO. In the maintenance plan backup tasks, the database is backed up only when the SMO state is in the NORMAL state if the Ignore databases where the state is not online check box is selected. After you apply this hotfix, the maintenance plan task now validates both the NORMAL state and any other state.

For example, the NORMAL | SHUTDOWN state is shown in SSMS if previous shutdown of the database completed without errors. The fix will make sure that databases in this state are also backed up by running the maintenance plan.

References

For more information about the Maintenance Plan wizard, visit the following Microsoft Developer Network (MSDN) website:

General information about the Maintenance Plan WizardFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft 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!

×