Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Overview of 64bit SQL

By Ram Kishore,

Microsoft® SQL Server™ 2000 Enterprise Edition (64-bit) provides full native support for the 64-bit version of the Microsoft Windows® operating system running on Intel Itanium Processors. This version of SQL Server 2000 provides many of the features of the 32-bit version, as well as providing support for 64-bit hardware. The 64-bit versions of Windows SQL Server 2000 and SQL Server 2000 Enterprise Edition combine to form a massive datacenter power plant capable of tackling today's most demanding database needs as well as future industry trends. It supports four languages: English, German, Japanese, and French.

Why 64-Bit Environment

The need for 64-bit technology is driven by applications that require high performance and address large amounts of physical and virtual memory.
Enterprises need 64-bit systems as they offer greater power, reliability and scalability. Primarily, a 64-bit machine can address more memory directly without using complex indexing or register-addressing schemes. Because internal memory is several orders of magnitude faster than storage, combining a 64-bit processing architecture with more RAM lets a processor pull more data into memory and operate on it directly, increasing performance manifold.

A 64-bit file system also can improve disk management. Rather than having to take a large disk, such as a 9 GB storage module, and segmenting it into 32-bit addressable chunks (2 GB each), you can address the entire disk. That can help, for example, in both database performance and the performance of the operating system itself.

The move to 64 bits will primarily help users who need to access very large data stores. This category includes applications such as CAD/CAM, science and engineering, human resources, online analytical processing (OLAP) and financial modeling. Users working with these computer-intensive applications will probably see immediate improvement with 64-bit machines over 32-bit machines running at the same clock rate and with similar memory configurations.

Product Highlights

Optimized to run on Itanium-based servers and Microsoft Windows® Server 2003, SQL Server 2000 Enterprise Edition (64-bit) delivers exceptional performance, reliability, and scalability; easy migration; and total cost of ownership (TCO) advantages for today's most demanding enterprise workloads.

Built to take advantage of hardware enhancements of the new breed of 64-bit servers, SQL Server 2000 Enterprise Edition (64-bit) offers higher levels of single-system scalability (scale-up) for the most memory-intensive data applications.

No longer, bound by the 32-bit memory limit of four gigabytes (GB), SQL Server 2000 (64-bit) is able to perform complex queries on large data sets without performance loss. Direct utilization of additional memory is made available to the system to use for essential database resources in order to increase throughput and performance. By expanding the headroom necessary to access large amounts of data and to support large numbers of concurrent database users and client applications, SQL Server 2000 (64-bit) enables new levels of scalability for enterprise applications.

There are application performance improvements through enhanced mathematic computational ability. The server can handle an increased number of users and connections through increases in memory capacity and it supports faster processors and parallel processing. These enhancements provide additional performance, scalability, and reliability for memory-intensive applications and workloads.

This definitely breaks the 4-gigabyte (GB)/64-GB memory limit of the 32-bit platform, based on the OS version. With the 64-bit platform, the operating system now supports more than 64 GB of physical and virtual memory. It also supports very large virtual memory, in the range of 16 terabytes.

Hardware error detection and prediction increases hardware reliability. Correctable and non-correctable errors are now reported in the event log. This allows the user to easily determine the exact cause of any hardware failure. The new hardware error detection, prediction, error checking, and notifications increase hardware reliability. This, in turn, increases reliability and availability of the 64-bit SQL Server 2000.

Compatibility with Existing SQL Server Installations

SQL Server 2000 Enterprise Edition (64-bit) ships a 64-bit database server, a 64-bit server agent, and a 64-bit analysis server with online analytical processing (OLAP) and data mining. These components of SQL Server 2000 Enterprise Edition (64-bit) are code compatible with the 32-bit version of SQL Server 2000, making it easy to integrate a 64-bit server with other SQL Server 2000 (32-bit) database servers. For database management and administration, 32-bit clients and SQL Server tools such as SQL Server Enterprise Manager and SQL Query Analyzer are easily used to remotely manage a SQL Server 2000 Enterprise Edition (64-bit) database.

Easy Migration from a 32-Bit SQL Server 2000 Database

By maintaining the same on-disk format on both 32-bit and 64-bit platforms, database administrators are able to protect key database investments made previously on a 32-bit server, easily moving user databases over to the new platform with minimal conversion effort. Migration is as easy as detaching the 32-bit database using a system- supplied stored procedure, transferring the user database to the 64-bit server’s disk sub-system, and attaching it to the 64-bit database server, again using a system- supplied stored procedure.

Client-Access Compatibility

Client applications that currently access SQL Server 2000 (32-bit) are able to easily connect to and access SQL Server 2000 (64-bit) without changes to application code. SQL Server 2000 (64-bit) supports client- access technology such as Microsoft ActiveX® Data Objects (ADO) and OLE DB, and maintains complete Transact-SQL code compatibility with the 32-bit version.

A Scalable Platform for Business Intelligence

Aggregating data acquired from multiple sources and adding them to the data warehouse is critical for providing enterprises with the ability to answer business analysis questions. With the ability of SQL Server 2000 (64-bit) to address additional memory on a single 64-bit server, complex dimension structures can now be stored in memory to analyze a large amount of data. Cube processing and cube querying are also enhanced by access to larger memory resources for caching, faster processing, and deeper analysis.

Support for High-Availability Configurations

SQL Server 2000 (64-bit) supports up to eight nodes in a failover cluster, enabling more complex high availability configurations. By allowing other 64-bit servers to back up critical applications in the event of planned or unplanned downtime, business operations are more protected and business applications are continuously available.

A Robust Platform for Server Consolidation

With the significant increase in memory capacity on 64-bit systems, enterprises now have an enhanced platform to consolidate their databases and database servers, requiring fewer machines to serve larger amounts of data. The ability of 64-bit hardware to support multiple processors also enables organizations to consolidate applications on fewer physical machines, each supported by SQL Server 2000 (64-bit).

The Choice for Your Enterprise Database Requirements

SQL Server 2000 Enterprise Edition (64-bit) scales to meet the demanding requirements of today's enterprises. Capable of addressing complex computations involving massive amounts of data processing, from data warehouse applications to natural science simulation applications, SQL Server 2000 Enterprise Edition (64-bit) provides the data management horsepower necessary for high-end enterprise applications. You now have the choice to implement your enterprise applications on SQL Server 2000 Enterprise Edition (64-bit), providing better performance and total cost of ownership compared to Unix-based database offerings. With database sizes rapidly increasing, SQL Server 2000 (64-bit) helps you to build and sustain a strategic advantage by efficiently managing your corporate data assets and keeping your company agile and responsive in today’s competitive market.

Addressing Industry Trends

Without question, the initial target market for SQL Server 2000 (64-bit) is the portion of the application market that requires memory-intensive workloads. The majority of these applications can be found in the following areas:

  • Data warehousing, data analysis, and decision support systems
  • Global-scale Web services
  • E-commerce applications with an unbounded number of users
  • Statistical modeling and analysis
  • Geo-spatial applications
  • Hosting scenarios

Today large database management, data mining, and decision support systems can benefit the most from adopting 64-bit Itanium 2-based systems, based on recent industry trends. Certain applications need to exceed the 4-GB address space limitation of 32-bit systems. An example is a database application, particularly those from data mining, memory-intensive workload, or an I/O-intensive workload applications. These three trends are among the top forces that drive our industry toward this next level of scalability:

  • Applications and data are growing in complexity and size. The size and complexity of applications and data continue to grow at an accelerated rate. Companies representing various industries are reporting that their databases are doubling in size every 9 to 15 months. Search the Web, poll the progressive companies today, and you will begin to see the rising number of customers whose database sizes are doubling. The current trend of improvements on processors is stated by the updated Moore's law, which now says, "Processor speed is doubling roughly every 18 months." 64-bit technology is intended to help the hardware industry keep up with the constant demand for more power.
  • High-end DBMS is becoming a requirement. As size and complexity of applications increase so do the demands on the database in the application. A rapidly increasing number of enterprise business and technical applications today are requiring a high-end data management platform that can meet the twin demands of high concurrency and scalable data management due to the breakneck rate at which they are amassing business data. Companies are seeing a significant increase in the size of databases in their organization, rapidly growing to extremely large dimensions.
  • Datacenters are consolidating. Limitations exist in both speed and physical space. Based on more than just the desire to save space, datacenter consolidation efforts have become popular in an effort to reduce the number of machines and associated management complexity and management cost.

As these industry trends begin to take shape, we will see other areas where SQL Server 2000 (64-bit) makes sense. One area that will eventually catch on is the value that 64-bit technology brings to the consolidation effort. Hardware vendors are in the process of releasing 64-bit computers that support up to 64 processors and theoretical limits of 32 TB of addressable memory. (At the time of this writing only 256 GB of memory is available on servers, but the industry is on track to support higher memory configurations within the next few months.) These servers will deliver a tremendous amount of processing power in a small footprint. SQL Server 2000 (64-bit) can provide native support for these servers at the same database price point as the 32-bit product. ISVs will eventually want to upgrade to 64-bit in an effort to help their customers achieve maximum headroom for large databases as well as maximum performance and scalability for common databases.

Migration Benefits

A migration from one version of software to another is typically no trivial matter. A great deal of planning is involved. Migration plans in general require costly consulting time, staff augmentation, and training. For the customer this inherent complexity was reduced with the migration from SQL Server 2000 (32-bit) to SQL Server (64-bit), because of the key compatibilities of the two platforms.

Benefits in the Migration Process

Migrating from a 32-bit version to a 64-bit version of SQL Server is neither difficult nor time-consuming. In fact, the process looks identical to a migration from one 32-bit SQL database to another. Because of the technical simplicity of a migration from a 32-bit version to a 64-bit version of SQL Server, building a migration strategy turns into a database targeting effort. The information provided in this white paper will be useful for the ISV, DBA, and developer communities to begin targeting specific databases that can benefit from 64-bit technology.

Deployment Benefits

SQL Server 2000 (64-bit) is a database product created by recompiling the SQL Server 2000 code base for the Itanium 2-based platform using the latest 64-bit compilers for Windows Server 2003. When migrating a database, the front-end application does not experience any difference other than performance. The database administrator can literally migrate databases one by one, without any modification to the client.

Licensing Benefits

Microsoft has designed the pricing and licensing of SQL Server 2000 (64-bit) to remain the same as its 32-bit counterpart. This allows customers to continue to benefit from the various licensing programs without having to rebudget new server deployments due to new or higher costs. For more details on licensing SQL Server 2000 (64-bit), visit the www.microsoft.com/sql/64-bit Web site.

Operational Benefits

The 32-bit and 64-bit versions of SQL Server are very similar. However, there are a few improvements to SQL Server 2000 (64-bit) as well as some inherited functionality from the 32-bit version that prove beneficial from the standpoint of day-to-day operations.

Maintenance Benefits

Microsoft Data Access Components (MDAC). MDAC is now managed by the underlying operating system, removing this responsibility from the DBA. Reducing the number of physical database servers to manage. Reducing the number of physical database servers was a big gain for the customer, not just in the area of datacenter consolidation, but also for maintenance and management costs. The price per application and the associated costs of maintaining multiple database servers began to drop as new database requirements were met with much less effort and expense.

On-Disk Format Benefits

Along with memory-intensive and performance-critical applications, SQL Server 2000 (64-bit) meets the demand for extremely large databases. The 64-bit version inherits the advanced on-disk database format from the 32-bit version which was designed to handle database sizes into the terabyte range. SQL Server 2000 (64-bit) will support ever-expanding amount of customer data.

Cluster Services Benefits

SQL Server 2000 (64-bit) provides the option to implement the application architecture on a failover cluster to provide high system and application availability.

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.

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.

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.

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

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.
  • CDW, also known as Copy Database Wizard, is also not available, because the needed DTS components are not available on the 64-bit platform.

SQL Mail

SQL Mail is not available on 64-bit SQL Server 2000. However, SQL Server Agent mail is supported. SQL Agent Mail in the 64-bit SQL Server can be configured remotely through Enterprise Manager if your client remotely connects using SQL Server 2000 Service Pack 3 or later. To configure SQL Agent mail, you must use Microsoft Outlook® Express. If you already have an SMTP Outlook Express profile created, you can use that profile for SQL Agent Mail by setting it up as a default account. The tools included are Network Utility, the Service Manger, and command-line utilities. To access the 64-bit version of management tools such as Enterprise Manager and Analysis Manager, you must use 32-bit tools on a 32-bit platform to remotely administer the 64-bit server.

Capacity

SQL Server 64-bit can support up to eight-node clusters. The AWE option is ignored because on this platform there is no practical memory limitation. You can see this AWE configuration parameter, but it is ignored by the 64-bit version of SQL Server 2000. A new option is added, affinity64 bit mask, and this is used to configure the processor affinity mask for the top 32 CPUs on a system that has more than 32 CPUs. A new startup option, -E, is added for file allocation extension.

Installation and Setup

After a site has identified its need for 64-bit and targeted the databases, the next task is to install SQL in preparation for the migration process. There is very little difference from the 32-bit version when it comes to installation. One of the biggest changes is the switch to Windows Installer. SQL Server 2000 (64-bit) now uses Windows Installer to completely integrate the installation of SQL Server components in a single feature tree. Notice that Analysis Services is no longer installed separately. The install procedure for SQL Server 2000 (64-bit) is very similar to that for the 32-bit version.

1. Insert the Microsoft SQL Server 2000 (64-bit) compact disc in your CD-ROM drive. If you are installing from a network location, share the installation folder and connect to the location from the computer where you want to install the program.
2. In the root folder of the compact disc or installation location on the network, double-click Setup.exe.
If a cluster is detected, Virtual server is the default selection. Otherwise, Local Instance is the only selection available.
3. Click Next twice.
4. On the Registration Information page, enter the user name, company, and product key, and then click Next.
5. On the Software License Agreement page, read the license agreement, and then click Yes to accept the license agreement. (Clicking No ends Setup.)
6. On the Feature Selection page, select or remove the components to be installed with SQL Server 2000.
7. To change how a feature is installed, click the icon to the left of the feature and select a different option.
8. To change the installation path, click the feature and then click Browse. However, you cannot change directories when Maintenance Mode is selected for a SQL Server instance.
9. Click Disk Cost to view calculated disk cost before adding or removing SQL Server components.
10. Click Next.
11. On the Instance Name page, you can choose to install either the default instance or a named instance. Do one of the following:
    - To install the default instance, click Default instance, and then click Next.
    - To install a named instance, click Named instance, type a name for the instance, and then click Next.
If a default instance has already been installed, all additional SQL Server instances on the machine must be named instances.
12. On the Service Account page, configure the logon account information for SQL Server 2000 service accounts. Select Advanced to configure service accounts separately.
13. On the Authentication Mode page, accept the default setting for Windows Authentication.
Whenever possible, use Windows Authentication. If you want to use Mixed Mode, click Help.
14. To identify the sa password, click Set an sa password, type and confirm your password in the fields provided, and then click Next.
Important You can no longer set a blank sa password due to security restrictions.
15. On the Cross-Database Ownership Chaining page, verify the cross-database ownership chaining security enhancement, and then click Continue.
Note Cross-database ownership chaining is not recommended and is turned off by default. However, after installation you can enable cross-database ownership chaining for individual databases. If you must use cross-database ownership chaining with all databases, select the check box. For security reasons, Microsoft recommends that you do not enable cross-database ownership chaining for all databases.
16. On the Collation Settings page, accept the default settings, and then click Next. (If you need to match collation settings in instances of SQL Server or to match the Windows locale of another computer, click Help instead.)
17. On the Error Reporting page, enable any error reporting you want for the SQL Server relational database engine, SQL Server Agent, and SQL Server Analysis Services, and then click Next.
18. On the Licensing Mode page, make selections according to your license agreement, and then click Next. (For information about licensing, click Help instead or see your system administrator.)
19. On the Ready to Install page, click Install to proceed with the installation.
20. On the Completing the Microsoft SQL Server Installation Wizard page, click Finish.

Log Files

When you run setup, log files are created in %TEMP% directory as sqlrunXX.log, and the general information file is created as sqlstpXX.log. Please note that sqlstpXX.log file is a general information file. The XX represents a enumerated number here.
The user can create a manual verbose log file by using the command-line switch /L*v. For example, if you want to create a verbose log file for your setup, at the command prompt you can use a command like setup.exe /L*v c:\Logfile.txt. This creates a manual verbose log file named Logfile.txt, it will put the log file into the c:\root directory, and you can point it to any directory you want. If a failure occurs, the quickest way to search the log is to find the first instance of Return Value 3 and look at what the output says.

Unattended Setup Parameters

Unattended setup is better because it has fewer command-line switches. Now we have /qb for quiet-mode with basic GUI, or you can use /qn for quiet mode with no GUI. We can also use the /settings parameter if we're using a setting file. You can always use setup.exe /? to find all the possible options, and it explains what command-line options it uses for what.

All setup parameters can be specified on a command-line. However, a settings file will make them easier to read and organize. To make things easier, a Template.ini file is provided on your CD. When you receive the CD or you go to the product CD, you will see the Template.ini file. This file explains each setup option in detail and gives examples of the options to use. The file is easy to create and easy to use to communicate exactly what you are installing or what you want to install.
Please note that we suggest providing a password at the command line instead of inside the Template.ini file. A Template.ini file exports its password in a .txt format. So if you put a password in a Template.ini file, then I would suggest that you remove the password after you have completed your setup.

Maintenance

For maintenance mode, Registry Rebuild and Rebuild Master are setup utilities used to repair corrupted installation. Registry Rebuild allows the user to repair the registry key associated with SQL Server. Rebuild Master allows the user to rebuild a system database without uninstalling and installing SQL Server. There are new options. The reinstall mode has two switches, omus or amus; omus for Registry Rebuild and amus for Rebuild Master database

Management Tools

Administrative tools such as Enterprise Manager, Query Analyzer, DTS, and Profiler can be used from a 32-bit computer to administer your 64-bit server. Locally installed tools include Service Manager, Server Network Utility, Books Online, Client Network Utility, and command- line tools such as OSQL, BCP, sqldiag, and others used for replication

Troubleshooting

For setup issues, check the final status in the verbose log file. You can create verbose log files manually at the command prompt using option /L*v. Do_sqlscript replaces cnfgsvr.exe, which we had before in 32-bit SQL Server 2000.

In the verbose log file, if Return Value 1, it is good. For an error or failure, search for Return Value 3 in the verbose log file. Identify the failed custom action and the reason why. Because in the verbose log file of setup we include the error reporting and error description to give you much more information and also some pointers.
For a successful installation, check the log files for "Installation completed successfully."

DTS components for 64-bit servers are not available in this release. DTS packages can be saved on 64-bit servers, and DTS packages can be run on the SQL Server 2000 64-bit dataset. But the package must be run from a 32-bit machine that is set up with 32-bit SQL Server tools.

The Copy Database Wizard is not available on 64-bit servers or target 64-bit servers. For data migration, you can use 32-bit SQL Server 2000 to 64-bit. You can use backup or restore, or the detach/attach database techniques. If you are using Meta Data Services to store the DTS package, you must manage and store the DTS packages on a 32-bit server, because MDS is not available on 64-bit SQL Server.

A linked server to a remote 32-bit SQL Server or remote 64-bit SQL Server will work fine. To link the server to any other data source, you need a 64-bit OLE DB provider from the vendor. Windows on Windows 64 is a 32-bit Windows subsystem that allows you to run 32-bit applications on 64-bit Windows. Because 32-bit applications run in an emulation mode, we would suggest running 32-bit applications on 32-bit hardware for optimal performance, and running 64-bit applications on 64-bit OSs.

Failover Clustering (64-bit)

In Microsoft® SQL Server™ 2000 Enterprise Edition (64-bit), failover clustering provides high availability support. For example, during an operating system failure or a planned upgrade, you can configure one node of a failover cluster to fail over to any other node in the failover cluster configuration. To install, configure, and maintain a failover cluster, use SQL Server Setup. As there are no previous 64-bit versions of SQL Server, you cannot upgrade an existing failover cluster to a SQL Server 2000 (64-bit) failover cluster. Also be aware that support for multiple instances of SQL Server differs in the failover clustering scenario: you can create multiple virtual servers in a cluster, but each virtual server can have only one instance of SQL Server installed. Use failover clustering to:

  • Install SQL Server on multiple nodes in a failover cluster. You are limited only by the number of nodes supported by the operating system.
    Before installing failover clustering, you must install the Microsoft Cluster Service (MSCS) and the 64-bit versions of the Windows® Server 2003 family (additional 64-bit versions of the Windows operating system for servers will be available for later releases of SQL Server 2000 [64-bit]). Because there is no 64-bit version of Windows NT® 4.0 or Windows 2000, you cannot install SQL Server 2000 (64-bit) with Windows NT 4.0 or Windows 2000.
  • Specify multiple IP addresses for each virtual server. With SQL Server 2000 (64-bit), you can specify multiple IP addresses for each server, which allows you to use all available network IP subnets. This provides alternate ways to connect if one subnet fails, and increasing network scalability. For example, with a single network adaptor, a network failure can disrupt communications. But with multiple network cards in the server, each network can be on a different IP subnet. If one subnet fails, at least one connection can continue to function. If a router fails, MSCS continues to function, and all IP addresses still work. However, if the network card on the local computer fails, communication still may be disrupted.
  • Administer a failover cluster from any node in the clustered SQL Server configuration.
  • Allow one virtual server to fail over to any other node in the virtual server failover cluster configuration..
  • Add or remove nodes from the failover cluster configuration using the Setup program.
  • Reinstall or rebuild a virtual server on any node in the failover cluster without affecting the other nodes.
  • Perform full-text queries by using Microsoft Search service with failover clustering.

Installing a New Failover Cluster

To install this release of SQL Server 2000 (64-bit) using the graphical user interface, follow these steps. For additional information about any steps in the Installation Wizard, click Help at the bottom of the page within the Wizard.

Before you create a Microsoft SQL Server 2000 (64-bit) failover cluster, you must configure Microsoft Cluster Service (MSCS) by using the Cluster Administrator in the 64-bit Microsoft Windows operating system. Note the group that contains the location of the cluster drive you want SQL Server to use by using the Cluster
Administrator before you run SQL Server Setup. You will need this information to create a new failover cluster.

1. Insert the SQL Server 2000 (64-bit) compact disc into your CD-ROM drive. If you are installing from a network location, share the installation folder and connect to the location from the computer where you want to install the program.

2. In the root folder of the compact disc or installation location on the network, double-click Setup.exe.

3. Click Start a new installation. Select Virtual Server, which is the default selection.

Note: This prompt appears only if there is a previously installed instance of SQL Server on the computer or if you are installing a failover cluster.

4. On the Welcome page, click Next.

5. On the Registration Information page, enter the user name, a company name, and the product key.

6. On the Software License Agreement page, read the license agreement and click Yes to accept the license agreement. Clicking No ends Setup.

7. On the Virtual Server Name page, enter a virtual server name. This name should be unique across the network.

8. On the Cluster Group Selection page, select the group that contains the drive you want to use for SQL Server under Available Cluster Groups. This designates the cluster group to locate the SQL Server virtual server resources. If you select the group containing the cluster quorum resource, a warning will be displayed recommending that you install to another group.

9. On the Failover Clustering page, enter one IP address for each network you wish to configure for client access.

10. On the Instance Name page, choose a default instance or specify a named instance. To install the default instance, click Default instance and then click Next. If a default instance has already been installed, all additional SQL Server instances on the machine must be named instances. To install a named instance, click Named instance and type a name for the instance.

Note: When installing a named instance, you must use ASCII characters below 128. This applies even if you have set the operating system's regional settings to a non-US locale, and non-English language.

Limitations

  • No upgrades from SQL Server 6.5 and 7.0
  • No remote installation
  • No English query
  • No Jet engine
  • No 32-bit tools (EM, QA, DTS Designer, Wizards, Development Tools)
  • However, 64-bit SQL Server can be remotely managed from a 32-bit client
  • No mixed 64-bit/32-bit processes are allowed. 64-bit program cannot call 32-bit MDAC DLLs from a 64-bit.
  • 16-bit program is not supported on 64-bit OS
  • No support for 32-bit kernel-mode code

For More Information

For the latest information on SQL Server 2000 (64-bit) check out the SQL Server 2000 (64-bit) Web site. Learn more about the 64-bit version of the Windows operating system on the Microsoft Windows Web site.

Total article views: 9876 | Views in the last 30 days: 8
 
Related Articles
FORUM

64-bit OS, 32-bit SQL Server 2000

Can 32-bit SQL Server 2000 run on 64-bit Windows Server 2003?

FORUM

Difference between 32-bit and 64-bit

Difference between 32-bit and 64-bit

FORUM

downgrade a database from sql2008 64-bit to sql2005 32-bit

downgrade a database from sql2008 64-bit to sql2005 32-bit

FORUM

SQL Server 2008 32-bit on Windows 2008 64-bit

SQL Server 2008 32-bit on Windows 2008 64-bit - Compatibility and Issues

FORUM

CLR sp running very slow on 64-bit virtual server...

CLR sp slow on 64-bit virtual server compared to 32-bit physical server

Tags
miscellaneous    
sql server 7    
 
Contribute

Join the most active online SQL Server Community

SQL knowledge, delivered daily, free:

Email address:  

You make SSC a better place

As a member of SQLServerCentral, you get free access to loads of fresh content: thousands of articles and SQL scripts, a library of free eBooks, a weekly database news roundup, a great Q & A platform… And it’s our huge, buzzing community of SQL Server Professionals that makes it such a success.

Join us!

Steve Jones
Editor, SQLServerCentral.com

Already a member? Jump in:

Email address:   Password:   Remember me: Forgotten your password?
Steve Jones