Microsoft KB Archive/813953

= Description of SQL Server 2000 64-bit Readme.htm additions =

Article ID: 813953

Article Last Modified on 11/13/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 64-bit Edition

-



SUMMARY
This article discusses several items that are not documented in the SQL Server 2000 (64-bit) Readme.htm file. This article is a supplement to the Readme.htm file instead of a replacement, so make sure that you read the Readme.htm file thoroughly.



MORE INFORMATION
 For better connectivity between a 32-bit client and SQL Server 2000 (64-bit), Microsoft recommends that you run Microsoft Data Access Components (MDAC) 2.7 Service Pack 1 or later on a 32-bit client computer. The Setup command line parameter reinstallmode=amus/omus is not supported on computers that are running failover clustering. The original released version of SQL Server 2000 (64-bit) can support up to 32 CPUs. For databases that are migrating from SQL Server 2000 32-bit to SQL Server 2000 64-bit, the 32-bit extended stored procedures will not work with SQL Server 2000 (64-bit). The Microsoft Windows on Windows 64 (WOW) environment in 64-bit Microsoft Windows will not run 32-bit SQL Server extended stored procedures (.dlls). The 32-bit extended stored procedures must be recompiled with a 64-bit compiler to obtain the 64-bit .dlls.

To build and to compile an extended stored procedure, you must know the locations of the following files:  Srv.h. You must use the 32-bit version that is available in SQL Server 2000. Opends60.dll. This file is available with SQL Server 2000 (64-bit). Opends60.dll is located in the \Mssql\Binn folder. Opends60.lib. This file is available with SQL Server 2000 (64-bit). Opends60.lib is located at the root of the media.</li></ul>

Note Microsoft provides a 64-bit compiler with the Microsoft Platform Software Development Kit (SDK). For additional information about the Microsoft Platform SDK, visit the following Microsoft Web site:

Microsoft Platform SDK

</li></ul>

<ul> If you use Console.exe, you must use the 32-bit version that is located in the Binn folder with Sqlservr.exe.

Note No 32-bit tools are included with this release of SQL Server 2000 64-bit. However, the tools that were ported to SQL Server 2000 64-bit can be installed by the Setup program. For a list of 64-bit tools, see SQL Server 2000 (64-bit Edition) Books Online for details.</li> Microsoft Windows on Windows 64 (WOW) is a 32-bit Windows subsystem that will permit you to run 32-bit applications on 64-bit Windows. However, 32-bit applications will be running in an emulation mode. Therefore, performance may not meet your expectations. Additionally, you might experience unexpected behavior when you run 32-bit applications on 64-bit Windows. Therefore, the SQL Server 32-bit management tools are not supported for running in WOW on 64-bit Windows. You must run them remotely on a 32-bit version of Microsoft Windows.

For more information about 32-bit tools and utilities, see the following topics: <ul> Microsoft SQL Server 2000 (64-bit) Readme File; topic: Section 3.4 - Tools and Utilities of the</li> SQL Server 2000 (64-bit Edition) Books Online; topic: Tools and Utilities - Differences Between 64-bit and 32-bit Releases (64-bit) - in

To download the SQL Server 2000 (64-bit Edition) Books Online version, visit the following Microsoft Web site:

SQL Server 2000 (64-bit Edition) Books Online

</li></ul> </li> The 64-bit MDAC components were included as core operating system components with the 64-bit version of Windows Server 2003. These 64-bit MDAC components were not included with SQL Server 2000 64-bit. SQL Server 2000 64-bit relies on the 64-bit MDAC components that are part of a 64-bit operating system. For more information, visit the following Microsoft Web site:

MDAC road map

</li></ul>

How to rebuild the master database on a Microsoft SQL Server 2000 (64-bit) cluster
Note These steps are also available in the following Microsoft Knowledge Base article:

817232 INF: How to rebuild the master database on a SQL Server 2000 (64-bit) cluster

You can rebuild the master database for an instance of SQL Server 2000 (64-bit).

To rebuild the master database, you must have the Product ID (PID) that was used to install SQL Server 2000 (64-bit). The PID is a GUID that is stored in the registry. For a default instance of SQL Server 2000 (64-bit), the PID is in the registry under the following registry key:

For a named instance of SQL Server 2000 (64-bit), the PID is in the registry under the following registry key:

When you rebuild the master database, you can configure:
 * The sa password.
 * The collation.
 * The cross-database ownership chaining.
 * The error reporting.

If you make changes to the authentication mode, the changes are not reflected after the server is reinstalled. However, you can change the authentication mode after the reinstallation is complete.

Note You must complete all these steps from the cluster node that owns the SQL Server resource.

To rebuild the master database of a default instance of Microsoft SQL Server 2000 (64-bit), follow these steps: <ol> Take the SQL Server virtual server offline.</li> In the Registry Editor, under the  registry key, make these changes: <ol style="list-style-type: lower-alpha;"> Change the SqlCluster value to 0, and note the value of SqlCLusterSec.</li> Change the value of SqlClusterSec to 0.</li></ol>

Note You must restore the value of SqlClusterSec after you rebuild the master database.

is the PID of the Windows Installer package that was used to install SQL Server.</li> Run Cliconfg.exe to start the Client Network Utility: <ol style="list-style-type: lower-alpha;"> On the Alias tab, click Add. The Add Network Library Configuration dialog box opens.</li> For Network Libraries, click to select the Other option button.</li> In the Server alias text box, type, where   is the name of the local computer. For a named instance, type \, where   is the name of the local computer, and   is the name of the instance of SQL Server. The local computer must be the cluster node that owns the SQL Server resource.</li> In the File name text box, type DBNETLIB .</li> In the Parameters text box, type LPC:. For a named instance, type LPC: \, where  is the name of the SQL Server virtual server, and   is the named instance of the SQL Server 2000 (64-bit) virtual server.</li> Click OK.</li></ol> </li> <li>Run Msiexec.exe to rebuild the master database. Here is an example:

From the command prompt, type the following

msiexec.exe /i <PID> REINSTALL=ALL REINSTALLMODE=amus SQLAUTOSTART=0 /L*v <Path and File_name.txt>

where  is the PID of the Windows Installer package that was used to install SQL Server, and   is the location and the file name for the verbose log file.

For example, type d:\rebuild_master_verbose_log.txt. The reinstallation dialog box appears. Make any changes to the sa password, collation, cross-database ownership chaining, and Watson. If you make changes to the authentication mode, they will not be reflected after the server is reinstalled. You can change the authentication mode after the reinstallation is complete.

Note Sometimes, the computer may display a message that states that file operations are pending, and you are prompted to restart the computer. Click No.</li> <li>In the Registry Editor, under the  registry key, change the SqlCluster value to 1. Restore the value of SqlClusterSec to the value you noted in step 2.</li> <li>Run Cliconfg.exe to open the Client Network utility. On the Alias tab, select the server alias that you created in step 3, and then click Remove.</li> <li>If the computer requests a restart, restart the computer that is running SQL Server now.</li> <li>Bring the virtual server online.</li></ol>

Analysis Services feature may not appear in the feature tree when you install a different edition
In some installation scenarios, Analysis Services may not appear as expected in the Setup feature tree where you select features for your installation of SQL Server 2000 (64-bit). This behavior may occur if you install an edition of Analysis Services after you remove a different edition of Analysis Services. To work around the problem, remove the  registry key after you remove one edition of Analysis Services but before you install a different edition.

Note This might only occur when you install a different edition of Analysis Services than the one that was originally installed. If the same edition of Analysis Services is reinstalled, the feature tree displays the Analysis Services feature as expected.

<div class="references_section">