FIX: System performance is decreased for user-mode applications on the server in the 64-bit version of Analysis Services (892589)
The information in this article applies to:
- Microsoft SQL Server 2000 Analysis Services
Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release. SUMMARYThis article describes the following about this hotfix
release: - The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix
package
- Whether you must restart your computer after you install
the hotfix package
- Whether the hotfix package is replaced by any other hotfix
package
- Whether you must make any registry changes
- The files that are contained in the hotfix
package
SYMPTOMSWhen you run the 64-bit version of SQL Server 2000 Analysis
Services, system performance is decreased for user-mode
applications on the server. For a list of all publicly released SQL
Server 2000 Post-Service Pack 3a hotfixes, see the following article in the
Microsoft Knowledge Base: 810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
CAUSEWhen you use the 64-bit version of Analysis
Services, files are opened in buffered mode. The operating system assigns extra
system file cache memory for files that are opened in buffered mode. As the
system file cache grows larger and larger, other user mode applications on the
server have their memory paged out to disk. When another user mode application
on the server performs a memory-intensive operation, system performance decreases. The performance decreases because stored data is retrieved from memory that has been paged out
to disk. RESOLUTIONHotfix informationA 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 Microsoft SQL Server 2000
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- SQL Server 2000 Service Pack 3 (SP3)
For information about how to obtain SQL Server 2000 SP3, see the
following article in the Microsoft Knowledge Base:290211 How to obtain the latest SQL Server 2000 service pack
- If you apply the SQL Server 2000 SP3-based version of this fix, the
server must be running SQL Server 2000 Analysis Services SP3.
- If you apply the SQL Server 2000 SP4-based version of this fix, the
server must be running SQL Server 2000 Analysis Services SP4.
Restart informationYou do not have to restart the server after you apply this hotfix.
The Analysis Services service is automatically stopped and restarted as part
of this hotfix. Registry information
You must change the registry. This hotfix implements calls
to trim the system file cache by using a thread in the Analysis Services
application. This hotfix creates the following two new registry entries: - Key=
HKLM\Software\Microsoft\OLAP Server\CurrentVersion
Name=
LimitSystemFileCacheSizeMB Value= (DWORD) This registry entry
specifies the target size for the system file cache. For example, a value of
8,192 MB gives you a maximum target size of 8 GB for the system file cache. A
zero value or a missing value disables this feature and enables the system
file cache to grow without limits. - Key= HKLM\Software\Microsoft\OLAP
Server\CurrentVersion
Name= LimitSystemFileCachePeriod Value=
(DWORD) This registry entry specifies the update period in milliseconds.
A zero value or a missing value gives you a default value of 500 milliseconds.
Between updates, the system file cache can grow larger than the target
size. However, the growth of the system file cache is limited by the bandwidth
of the hard disk. For example, a 50 MB per second hardware limit restricts the
growth of the system file cache to 25 MB in 500 milliseconds. Note To change these registry entries, you must be running the Analysis Services service. You must be running this service under an account that has SE_INCREASE_QUOTA_NAME permissions. Hotfix file informationThis hotfix contains only those files that are required to correct
the issues that this article lists. This hotfix may not contain of 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 tool in Control Panel. SQL Server 2000 32-bit versions|
Tempcatsign.cdf | Not
Applicable | 956 | 19-Jan-2005 | 04:22 | Not
Applicable | Msdmine.dll | 8.0.1002.0 | 1,380,944 | 19-Jan-2005 | 03:48 | x86 | Msmd.h | Not
Applicable | 18,800 | 31-Dec-2004 | 20:30 | Not
Applicable | Msmdcb80.dll | 8.0.1002.0 | 221,760 | 19-Jan-2005 | 03:48 | x86 | Msmddo80.dll | 8.0.0.1002 | 4,076,104 | 19-Jan-2005 | 03:48 | x86 | Msmdgd80.dll | 8.0.1002.0 | 1,036,864 | 19-Jan-2005 | 03:48 | x86 | Msmdpump.dll | 8.0.1002.0 | 172,608 | 19-Jan-2005 | 03:48 | x86 | Msmdsgn.rll | 8.0.1002.0 | 446,524 | 19-Jan-2005 | 03:19 | Not
Applicable | Msmdsgn80.dll | 8.0.0.1002 | 9,642,572 | 19-Jan-2005 | 03:48 | x86 | Msmdsrv.exe | 8.0.1002.0 | 1,851,972 | 19-Jan-2005 | 03:48 | x86 | Msmdvldm.exe | 8.0.1002.0 | 1,401,408 | 19-Jan-2005 | 03:48 | x86 | Msolap80.dll | 8.0.1002.0 | 2,089,552 | 19-Jan-2005 | 03:48 | x86 | Msolap80.rll | 8.0.1002.0 | 213,068 | 19-Jan-2005 | 02:06 | Not
Applicable | Sqlstpcustomdll.dll | 1.0.88.0 | 823,296 | 11-Jan-2005 | 19:02 | x86 | Sqlstpcustomdll.rll | Not
Applicable | 22,528 | 11-Jan-2005 | 19:02 | Not
Applicable |
SQL Server 2000 64-bit version|
Sqlrun.msp | Not
Applicable | 11,839,488 | 19-Jan-2005 | 19:40 | Not
Applicable | Note Because of file dependencies, the most recent hotfix or feature
that contains these files may also contain additional files. WORKAROUNDYou cannot set an
explicit limit in the operating system for the system file cache. To impose some control over the size of the system file cache, flush
the system file cache at set intervals. The only way to flush the system file
cache information is to make a call to the NtSetSystemInformation function, and then specify the
target size for the system file cache. The call to the NtSetSystemInformation
function causes the operating system to flush the system file cache. This action releases memory to reach the target size. Additionally, there is no explicit way to keep the system
file cache at or lower than the specified target size. You must make calls to the NtSetSystemInformation function at set intervals.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/25/2006 |
---|
Keywords: | kbfix kbbug kbHotfixServer kbQFE kbpubtypekc KB892589 kbAudDeveloper kbAudITPRO |
---|
|