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 R2, Microsoft SQL Server 2008, and Microsoft SQL Server 2005 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 R2, SQL Server 2008, or SQL Server 2005 fix release.

Symptoms

Consider the following scenario:

  • You run the DBCC CHECKDB('master') command on a computer that is running SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2.

  • The user account that you use to run the command is not assigned to the sysadmin fixed server role or is not mapped to the 'dbo' user role.

  • You receive a successful DBCC result.

In this scenario, you receive an error message that resembles the following below the DBCC result:

Msg 7983, Level 14, State 36, Line 2
User 'guest' does not have permission to run DBCC checkdb for database 'mssqlsystemresource'.

Resolution

Cumulative update information

SQL Server 2005 Service Pack 4

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

2464079 Cumulative update package 1 for SQL Server 2005 Service Pack 4Note 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 2005 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:

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

SQL Server 2005 Service Pack 3

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

2345449 Cumulative update package 12 for SQL Server 2005 Service Pack 3Note 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 2005 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:

960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. 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 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 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:

2289254 Cumulative update 1 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. 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:

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

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 10 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:

2279604
Cumulative update 10 for SQL Server 2008 Service Pack 1
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 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:

970365
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 3. 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:

2261464 Cumulative update package 3 for SQL Server 2008 R2Note 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

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 about DBCC CHECKDB (Transact-SQL), visit the following Microsoft Developer Network (MSDN) website:

DBCC CHECKDB (Transact-SQL)For more information about PowerPivot components and tools, visit the following Microsoft Developer Network (MSDN) website:

PowerPivot components and toolsFor more information about the Installation of PowerPivot for SharePoint software, visit the following MSDN website:

Installation (PowerPivot for SharePoint)For 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 problems

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499New 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

More Information

Steps to reproduce this problem in SQL Server 2008 R2

  1. Create a new SQL Server 2008 R2 database. For example, create a SQL Server 2008 R2 database by using the "test" database name.

  2. Create a new SQL login. In the Login name field, enter a login name. For example, enter LoginForUserA.

  3. In the Default database field, select the database that you created in step 1.

  4. Create a new user in the database that you created in step 1.

  5. Select the login name that you created in step 2 as the login name.

  6. Select the db_owner check box in the Database role membership section, and then click OK.

  7. Create a new user in the master database by using the same user name that you used in step 4.

  8. Repeat step 5 to step 6 in the master database.

  9. Connect to the server by using the login that you created in step 2.

  10. Run the following command:
    SELECT USER
    The user name that you created in step 4 is returned.

  11. Run the following command:
    DBCC CHECKDB('master')

The CHECKDB runs successfully and the following message is returned:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'master'.

However, the error message that is described in the "Symptoms" section is returned unexpectedly when the mssqlsystemresource database is checked.

Facebook LinkedIn Email
SUBSCRIBE RSS FEEDS

Need more help?

Want more options?

Discover Community

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

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

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

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders

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!

×