Export (0) Print
Expand All

Differences Between 64-bit and 32-bit Releases (64-bit)

SQL Server 2000

  This topic applies only to SQL Server 2000 (64-bit).

This section describes differences you need to consider when installing and using the 64-bit version of Microsoft® SQL Server™ 2000.

Setup and Installation

Windows Installer-Based

SQL Server 2000 (64-bit) uses the Windows Installer to completely integrate the installation of SQL Server features in a single feature tree. Minimum and typical installation modes are no longer implemented. Setup initially displays the feature tree with all available features selected. Administrators can customize installations by choosing items on the feature tree and changing installation paths.

Setup Feature Tree Interaction with Parent/Child Features

In this release of SQL Server 2000 (64-bit), child feature selection is more limited than in the 32-bit version of SQL Server 2000. For example, the Tools feature installs all tools; there is no option to select individual tools. Similarly, Server Components are limited to SQL Server and the Full-Text Search Engine. The full selection of child features will be enabled in the next major release.

Connectivity-Only Option Not Supported

The Connectivity-Only option is not implemented during the SQL Server 2000 (64-bit) Setup. The Connectivity-Only option in previous versions installed Microsoft Data Access Components (MDAC) and JET. JET is not available for the 64-bit version of SQL Server 2000. MDAC 64-bit components are installed by the 64-bit versions of the Windows® Server 2003 family as part of its core components.

Remote Installation

SQL Server 2000 (64-bit) does not support remote installation.

Previous Version Upgrades

Previous versions of SQL Server for the 32-bit computer are not supported to run on the 64-bit platform; upgrades of 32-bit instances are not supported in this release.

Data Migration

Data migration from SQL Server 2000 to SQL Server 2000 (64-bit) is supported. Attaching a 32-bit database to a 64-bit instance is possible by using detach/attach or backup/restore in 32-bit Enterprise Manager. You can move databases back and forth between 32-bit and 64-bit versions of SQL Server. Migrating data from SQL Server version 7.0 is also supported using the same methods. Downgrading data to SQL Server 7.0 from SQL Server 2000 (64-bit) is not supported.

Documentation for Both SQL Server 2000 SP3 and SQL Server 2000 (64-bit)

This release of Books Online includes documentation for both SQL Server 2000 Service Pack 3 (SP3) and SQL Server 2000 (64-bit). The Books Online table of contents is organized by platform:  64-bit content is grouped together in a node entitled "SQL Server 2000 (64-bit)," and 32-bit topics are grouped together in a node called "SQL Server 2000."

Content specific to the 64-bit platform is identified below the topic title as follows: "This topic applies only to SQL Server 2000 (64-bit)." All 64-bit topics also include "64-bit" in the topic title. Topics that include content for SP3 changes in behavior include the following tag below the topic title: "New Information – SQL Server 2000 SP3." Not all 32-bit topics have been updated for SP3.

Index entries for 32-bit and 64-bit content have been combined. As a result, keyword searches may return a combined list of 32-bit and 64-bit topics. Topics that apply to the 64-bit SQL Server can be identified by the "64-bit" tag in the topic title, and also by the tag below the topic title that states, "This topic applies only to SQL Server 2000 (64-bit)."

Maintenance

Feature Maintenance

SQL Server 2000 (64-bit) uses Add or Remove Programs in Control Panel to fully support the addition and removal of individual features, as well as to remove instances of SQL Server. You can also use the Setup user interface or command line for installation maintenance. Feature maintenance for clustered installations is not supported.

Instance Maintenance

Maintenance activities on existing installations are supported with Add or Remove Programs in Control Panel as well as by the Setup program. Each installed instance (except for clustered installations) is listed in the Add or Remove Programs dialog box. Any non-cluster instance may be removed or changed with the Add or Remove Programs. Instance maintenance may also be performed on the setup command line by specifying features on the command line or in an .ini file. For information about cluster maintenance, see the section on failover clustering at the end of this topic.

Editions and Components

Supported Editions

For this release, only the Enterprise Edition is available. The SQL Server 2000 (64-bit) Desktop Engine is not available.

Network Libraries

The Network Library configuration page is not included in SQL Server 2000 (64-bit). Setup initially enables Shared Memory, Named Pipes, and TCP/IP. Use the SQL Server Network Utility to change the settings that enable or disable protocols. Configuration of Network Libraries is not supported in Setup, but is still supported by the SQL Server Network Utility. Configure client network libraries using the Client Network Utility (cliconfg.exe) included with the 64-bit versions of the Windows Server 2003 family.

Services

The Service Account dialog supports the SQL Server Service (MSSQLSERVER, MSSQL$<instancename>), the SQL Agent Service (SQLSERVERAGENT, SQLAgent$<instancename>), and the Analysis Services (MSSQLServerOLAPService) account. The Remote Account Information dialog supports the Cluster Setup Admin account for use when installing a virtual server. Command-line support for configuration of these accounts is also provided.

Code Samples

Code samples are not installed by Setup.

English Query

English Query is not supported.

Analysis Services

Analysis Services Integrated into SQL Server Setup

Analysis Services can be installed at the same time as the SQL Server relational database engine and other SQL Server components. It is part of the Windows Installer feature tree, in which you can select the features you want to include in your installation. Analysis Services appears in the feature tree with Data and SQL Repository child features.

Analysis Services Uses the SQL Server Repository

The 64-bit version of Analysis Services uses SQL Server instead of Jet (.MDB) for its meta data repository. If the full SQL Server is not installed with Analysis Services, the SQL Repository child feature installs the core SQL Server files and enables you to specify the location of these files.

Tools and Utilities

Graphical User Interface Management Tools

To administer a 64-bit SQL Server or Analysis Server with management tools like Enterprise Manager or Analysis Manager, you must use the 32-bit tools on a 32-bit server to remotely administer the 64-bit server. The only 64-bit tools included with this release are the Server Network Utility, the Service Manager, and the command line utilities.

Distributed Transaction Coordinator (DTC) Installed with the 64-bit versions of the Windows Server 2003 family

DTC is part of the 64-bit versions of the Windows Server 2003 family operating system and is no longer installed as part of the SQL Server 2000 (64-bit) setup. The DTC service can no longer be managed from the SQL Server Service Manager. To manage this service, use Services in the 64-bit versions of the Windows Server 2003 family Administrative Tools.

Data Transformation Services (DTS) components for 64-bit servers are not available in this release. Note the resulting functionality changes:

  • A DTS package can be saved on the 64-bit server, and a DTS package can be run against a SQL Server 2000 (64-bit) dataset, but the package must run from a 32-bit machine that is set up with SQL Server 2000 tools.

  • The Copy Database Wizard will not be able to run on a 64-bit server or target a 64-bit server. Data migration from SQL Server 2000 to SQL Server 2000 (64-bit) is supported. Attaching a 32-bit database to a 64-bit instance is possible by using either the detach/attach or the backup/restore technique. You can move databases back and forth between 32-bit and 64-bit versions of SQL Server.

  • If you are using Meta Data Services (MDS) to store a DTS package, you must manage and store the DTS package on a 32-bit server.

  • Transformable push subscriptions are not supported. Pull subscriptions from a 32-bit installation of SQL Server 2000 should work with a 64-bit Publisher or Distributor.

SQL Mail

SQL Mail is not supported in this release of SQL Server 2000 (64-bit). The following extended procedures and stored procedures are not supported, as they are part of the SQL Mail functionality:

  • xp_startmail

  • xp_stopmail

  • xp_sendmail

  • xp_readmail

  • xp_deletemail

  • xp_findnextmsg

  • sp_processmail

    However, SQL Agent Mail in SQL Server 2000 (64-bit) can be configured remotely by Enterprise Manager, if your client remotely connects using SQL Server 2000 Service Pack 3.0 or later.

    To configure SQL Agent Mail, you must use Microsoft Outlook® Express to use an existing mail account.

To create a mail account for SQL Agent Mail using Outlook Express

1. From the Start menu, select Outlook Express.

2. From the Tools menu, select Accounts. . .

3. On the Internet Accounts dialog box, click Add, and then click Mail. This will allow you to create a new mail account by launching the Internet Connection Wizard.

4. On the Your Name dialog box in the Display name box, enter the name you would like to be the sender of all SQL Agent e-mail messages.

5. On the Internet E-mail Address dialog box in the E-mail address box, enter the e-mail account to use to send SQL Agent e-mail messages. For example: someone@example.com.

6. On the E-mail Server Names dialog box in the My incoming mail server is a box, select POP3 for the server type.

7. In the Incoming mail (POP3, IMAP, or HTTP) server box, enter the name of the POP3 server. If you are only using this account for SQL Agent Mail, it is not necessary to select a valid POP3 server name, as SQL Agent Mail does not receive mail.

8. In the Outgoing mail (SMTP) server box, enter a valid SMTP server name to be used to send SQL Agent messages.

9. On the Internet Mail Logon dialog box in the Account Name box, enter the account you wish to use for sending SQL Agent Mail notifications.

10. Click Next.

11. Click Finish.

If you are using Outlook Express 6.0 or later, you must configure this application so that it does not send an alert when SQL Agent Mail is accessing your Outlook Express account.

To configure SQL Agent Mail with Outlook Express 6.0

1. From the Outlook Express Tools menu, select Options . . .

2. Select the Security tab, and clear the "Warn me when other applications try to send mail as me" check box.

3. Click OK.

If you already have an SMTP Outlook Express profile created, you can use that profile for SQL Agent Mail by setting it as the default account.

To use an existing SMTP Outlook Express Mail Account for SQL Agent Mail

1. From the Start menu, select Outlook Express.

2. From the Tools menu, select Accounts. . .

3. On the Internet Accounts dialog box, select the mail account to set as the default, and click the Set as Default button. This must be a POP3/SMTP account for SQL Agent Mail to work.

If you would like to change the name of your mail account after you have set it as the default, you can rename it to SQLAgentMail. The same mail account name will be used in configuring SQL Agent Mail in Enterprise Manager.

To change the name of your profile for SQL Agent Mail

1. From the Start menu, select Outlook Express.

2. From the Tools menu, select Accounts. . .

3. On the Internet Accounts dialog box, select the default account and click the Properties button.

4. On the Properties dialog box, type the name for the profile in the Mail Account box.

After you have created a mail account for SQL Agent Mail, you can configure SQL Agent Mail using Enterprise Manager.

To select the mail account in Enterprise Manager for SQL Agent Mail

1. On the Agent Properties dialog box, select the General tab.

2. In the Mail profile box, select the previously configured Outlook Express mail account.

For more information about SQL Agent Mail functionality, see the 32-bit SQL Server 2000 Books Online.

Client Tools Only

Installing only the Tools feature from the feature tree can facilitate a Client Tools Only installation. Note that the SQL Server graphical user interface management tools are not included with this release, except for the SQL Server Network Utility and the Service Manager. The command-line tools are available.

Supported Tools

Tools must be installed from the SQL Server 2000 (64-bit) RTM CD. Tools from any other CD cannot be installed as part of an instance of SQL Server 2000 (64-bit). To utilize management tools like Enterprise Manager, use a 32-bit instance of SQL Server where management tools are installed to remotely administer instances of SQL Server 2000 (64-bit).

Record Unattended File

A Template.ini file is provided and can be modified for unattended installations. SQL Server 2000 (64-bit) does not support the record unattended file functionality.

Development Tools

The Development Tools feature is not included in the feature tree. The SQL Debugging Interface (SDI) is installed by Setup, but is included in the core SQL Server Engine component. The other development tools available in SQL Server 2000 (32-bit) (headers and libraries, MDAC SDKs, and the Backup/Restore API) are not installed by Setup.

For more information on MDAC and the status of its components, see the MDAC Roadmap

DB-Library

The DB-Library programming model is not supported in SQL Server 2000 (64-bit), and it has not been ported to the 64-bit Windows operating system. The DB-Library API has not been enhanced beyond the level of SQL Server version 6.5. All DB-Library applications can work with SQL Server 2000, but only as 6.5-level clients. Features introduced in SQL Server 2000 and SQL Server version 7.0 are not supported for DB-Library applications.

Registry Rebuild and Rebuild Master

Registry Rebuild and Rebuild Master are implemented differently in the 64-bit version of SQL Server 2000 than in the 32-bit version. In the 64-bit version, SQL Server 2000 takes advantage of the self-repairing features provided by Windows Installer. In addition, the REINSTALL and REINSTALLMODE properties on the setup command line are available to explicitly rebuild the registry, reinstall corrupted or missing files, reinstall corrupted or missing shortcuts, and rebuild the master databases. These properties can be specified on the command line or in an .ini file.

Failover Clustering

Cluster Support

Installation of a failover cluster is supported for a single cluster definition. Feature maintenance for clustered installations is not supported. A template .ini file is provided that enables all supported cluster features.

Cluster Maintenance

Because only a single cluster definition is supported, feature maintenance with Add or Remove Programs in Control Panel for clustered installations is not supported. Clustered instances are displayed by Add or Remove Programs, but changes are not allowed. Setup supports adding or removing a node with either the graphical user interface or the command line. Setup also supports changing or adding an IP address. Cluster uninstall is supported by Setup.

Show:
© 2014 Microsoft