How to improve the performance of a server that is running SQL Server 2000 if the server has case-insensitive collation and is hosting a Project Server 2003 database

This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
INTRODUCTION
This article describes how to improve the performance of a server that is running Microsoft SQL Server 2000 if the server has case-insensitive collation and is hosting a Microsoft Office Project Server 2003 database.
More information
Important Enable this change only on a case-insensitive collation server that is running SQL Server 2000. Slow performance can occur during a save operation or at any time that you are writing to the back-end tables when the following conditions are true:
  • There are lots of resources that are involved in the save operation. The recommended number of resources in an Enterprise Resource Pool is 1500 to 2000.
  • The server that is running SQL Server 2000 is set to use collation that is case insensitive. A select query is run during the save operation that converts text strings to all lowercase letters to allow for the uniqueness of the resource names. The select query is needed when the server that is running SQL Server 2000 is set to use collation that is case insensitive. However, the select query adds another step to the query process. This step is not required when the collation is case sensitive.
To improve the performance of a case-insensitive collation server that is running both SQL Server and Project Server 2003, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  1. Install Microsoft Office Project Server 2003 Service Pack 2a (SP2a).

    For more information about Project Server 2003 Service Pack 2a, click the following article number to view the article in the Microsoft Knowledge Base:
    873458 How to obtain the latest service pack for Project Server 2003
  2. Locate the folder that contains the Project Server 2003 Connection Information tool. Then, double-click ConnInfo.exe.

    The ConnInfo.exe tool is located in the following folder on the computer that is running Project Server 2003:
    drive:\Program Files\Microsoft Office Project Server 2003\Bin\1033
    To download the ConnInfo.exe tool, visit the following Microsoft Web site:
  3. At the end of the existing value in the SQL Server box, type the following:
    ;SqlCaseInsensitive=true;
  4. Click Save.
  5. Quit the Project Server 2003 Connection Information tool.
Note If you restart the Project Server 2003 Connection Information tool, you will notice that the SqlCaseInsensitive string is now missing. If you save the Project Server 2003 Connection Information dialog box settings without re-adding the SQLCaseInsensitive string, the SQLCaseInsensitive string will be removed from the connection string. Therefore, the change will be disabled. You must add the SQLCaseInsensitive string every time that the Project Server 2003 Connection Information tool is run.
projectserver2003 projectserver2k3 prjsvr2003 prjsvr2k3
Properties

Article ID: 906687 - Last Review: 01/16/2015 01:46:14 - Revision: 6.0

  • Microsoft Office Project Server 2003
  • kbnosurvey kbarchive kbqfe kbservicepack kbupdate kbprojectserver2003sp2fix kbfix kbbug kbhowto KB906687
Feedback