Microsoft KB Archive/283040

= INF: Readme.txt for SQL Server 7.0 Service Pack 3 (Continued) =

Article ID: 283040

Article Last Modified on 7/19/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition
 * Microsoft SQL Server OLAP Services

-



This article was previously published under Q283040



SUMMARY
This article is a continuation of the Readme.htm file in Q274798 for Service Pack 3 (SP3) for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0.



5.12 The French Version of SQL Server Books Online
Introduced in Service Pack 1

The original French version of SQL Server Books Online had an incorrect table of contents. The French version of the Database Components SP3 includes a self-extracting file that contains a new French SQL Server Books Online file with a corrected table of contents.

To install the corrected French version of SQL Server Books Online:


 * 1) Copy the file Sqlbolfr.exe from the service pack directory to an empty folder on your computer.
 * 2) Execute Sqlbolfr.exe to extract the file Sqlbol.chm.
 * 3) Copy this new Sqlbol.chm to the C:\Mssql7\Books directory. This will overwrite the incorrect version of the file.

5.13 SQL Server Clustering White Paper
The white paper &quot;How to Install SQL Server 7.0, Enterprise Edition, on Microsoft Cluster Server: Step by Step Instructions&quot; supplements the clustering information provided in SQL Server Books Online for SQL Server 7.0. For more information about the white paper, see http://www.microsoft.com/sql/prodinfo/previousversions/whitepapers.mspx.

5.14 New Database Option
Introduced in Service Pack 2

Database Components SP2 introduced a new pending upgrade database option to support functionality that will be introduced in a future version of SQL Server. Full instructions for using this option will be included in the documentation of the future version of SQL Server.

When the pending upgrade option is set to TRUE users cannot create indexes or statistics in the database. Attempts to create indexes or statistics receive the new error message 1931:

Create index/Create statistics is disallowed when the database has pending upgrade enabled.

However, if the pending upgrade option is set to TRUE while a clustered index is being created and there are no existing nonclustered indexes, the index creation will succeed.

On the other hand, if nonclustered indexes already exist when the creation of clustered index is initiated, and the pending upgrade option is set to TRUE while index creation is going on, the index creation may fail, rolling back the whole operation.

The pending upgrade option should always be set to FALSE for any SQL Server 7.0 system that is not inter-operating with the future version of SQL Server: sp_dboption 'database_name', 'pending upgrade', 'FALSE' sp_dboption reports the status of the pending upgrade option if the stored procedure is called with no parameters, or with only the dbname parameter, for example: sp_dboption 'Northwind' The DATABASEPROPERTY function supports a new IsPendingUpgrade property to report the status of the pending upgrade database option, for example: DATABASEPROPERTY(Northwind, IsPendingUpgrade) IsPendingUpgrade returns 0 if pending upgrade is FALSE, 1 if pending upgrade is TRUE.

5.15 New sqlservr Startup Option
Introduced in Service Pack 2 Database Components SP2 introduced a new –g startup switch for the sqlservr command prompt utility:

-g memory_to_reserve

Specifies an integer number of megabytes (MB) of memory that SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. The memory pool is the area used by SQL Server for loading items such as extended stored procedure .dll files, the OLE DB providers referenced by distributed queries, and OLE Automation objects referenced in Transact-SQL statements. For more information about SQL Server memory management, see Memory Architecture in the SQL Server Books Online for SQL Server 7.0.

The default value for this option is 128 MB. If this option is not specified, the default value is suitable for a wide range of run-time environments. Using this option may help tune memory allocation, but only when physical memory on the server exceeds 2 gigabytes (GB) for the SQL Server Desktop or Standard editions, or 3 GB for SQL Server Enterprise Edition. Configurations with less physical memory will not benefit from using this option.

Use of this option may be appropriate in large memory configurations in which the memory usage requirements of SQL Server are atypical and the virtual address space of the SQL Server process is totally in use. Incorrect use of this option can lead to conditions under which SQL Server may not start or may encounter run-time errors.

You should use the default for the -g parameter unless you see the following warning in the SQL error log:

Warning: Clearing procedure cache to free contiguous memory.

This message indicates that SQL Server may be trying to free parts of the SQL Server memory pool to find space for items such as extended stored procedure .dll files or OLE Automation objects. In this case, consider increasing the amount of memory reserved by the -g switch. Using a lower value than the default will increase the amount of memory available to the buffer pool and thread stacks, which may, in turn, provide some performance benefit to memory intensive workloads in systems that do not use many extended stored procedures, distributed queries, or OLE Automation objects.

5.16 Repository Changes
Introduced in Service Pack 2 This section documents the changes introduced in the Repository by the service pack.

5.16.1 Importing from DB2 and Informix Databases
Introduced in Service Pack 2 When using OLE DB Scanner to import from DB2 or Informix databases, Microsoft Repository now creates tables for schema and type information. This functionality applies to databases using the Microsoft ODBC Driver for DB2 and the Intersolv Informix ODBC Driver, the Intersolv OLE DB Driver for ODBC, and the Intersolv OLE DB Provider for Informix.

5.16.2 Improved Retrieval of Versioned Objects
Introduced in Service Pack 2 You can now retrieve the most recent object version in all cases, even when the version sequence includes a deleted version. Previously, if you deleted an object version and then created a new object version, attempting to retrieve the most recent version produced an error.

Keywords: kbinfo KB283040

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.