FIX: The SQL-DMO SpaceAvailableInMB property of the Database object may return an incorrect value in SQL Server 2005 or in SQL Server 2000 (919609)



The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Developer Edition 64 bit
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
  • SQL Server 2005 Standard Edition for Itanium-based Systems

Bug #: 780 (Shiloh)
Microsoft distributes 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 2005 fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for applying the hotfix package
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005 or in Microsoft SQL Server 2000, you use the SQL Distributed Management Objects (SQL-DMO) SpaceAvailableInMB property of the Database object. You do this to determine the space that is allocated and that is unused in the operating system files that implement a database. In this scenario, the SQL-DMO SpaceAvailableInMB property of the Database object may return an incorrect value. Typically, you experience this problem when the database size exceeds 2 terabytes.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

If you are running any version of SQL Server 2000 or SQL Server 2005 without Service Pack 1, you must upgrade to the Microsoft SQL Server 2005 Backward Compatibility Components. For information about how to obtain the SQL Server 2005 Backward Compatibility Components, visit the following Microsoft Web site:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.SQL Server, 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Sqldmo.dll2000.85.1800.04,562,94403-Jun-200602:05x86
SQL Server, 64-bit version
File nameFile versionFile sizeDateTimePlatform
Sqldmo.dll2000.85.1800.06,476,28803-Jun-200602:50x64
SQL Server, Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Sqldmo.dll2000.85.1800.014,517,76003-Jun-200602:28IA-64

WORKAROUND

To work around this problem, use the sp_spaceused system stored procedure to obtain the correct database size.

STATUS

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

MORE INFORMATION

For more information, 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


Modification Type:MajorLast Reviewed:8/7/2006
Keywords:kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB919609 kbAudDeveloper kbAudITPRO