What Happens If I Select the Custom Install Option?
What Happens If I Select the Custom Install Option?
If you select the Custom option for the installation, I assume you either want everything you possibly can get or you have a specific need to alter the collation settings for your installation. The Custom installation option gives you more steps than if you had selected the Typical installation option.
The first extra screen you see is the Select Components screen. This enables you to select or remove components that are either not covered by the Typical installation (such as code samples and add-ons) or that you do not require in your installation.
Within this screen you can add the code samples that ship with SQL Server 2000 to help you when developing client applications to talk to your database. This option is sneakily hidden right at the bottom of the list box on the left. To select it, click the check box.
After you’re satisfied with the components you have selected, click Next to proceed with the installation.
The next screen you see is the Authentication Mode screen.
This screen enables you to set the user account password for the SQL Server 2000 System Administrator (sa). Make sure you enter a password you will not easily forget and that others will not be able to guess too easily.
The next screen you see is the Collation Settings screen.
This is where things begin to get interesting. If you need to talk to another instance of SQL Server that has a different Windows locale or collation setting from your machine, you must adjust the setting to that of the instance of SQL Server you want to connect to. The instance can be running on a remote machine or on your PC. For our requirements, we do not need to do this, but if the need grabs you…
The locale refers to the way the characters on your computer are displayed and stored. The locale is set for your machine when the operating system is installed. Various countries and languages use different locale settings to enable the unique characters of their languages to be displayed. For example, the U.S. English character set uses the Latin I_General locale.
The next setting you must ensure is correct is the Sort Order option. The following options enable different combinations of sort orders:
Binary—The fastest sort order, it is always case sensitive. This means that lowercase will always come before uppercase. For example, “m” will always appear before “M.” If Binary is selected, the Accent and Case sensitive sort order options are grayed out.
Case sensitive—Forces SQL Server 2000 to evaluate the case of the character. Lowercase will always come before uppercase. For example, “a” will always appear before “A.” If this option is not selected, SQL Server 2000 considers “a” and “A” to be equal.
Accent sensitive—Forces SQL Server 2000 to evaluate accented and unaccented characters. For example, “a” will not be equivalent to “a.” Like case sensitive, if Accent sensitive is not selected, SQL Server 2000 considers the accented and unaccented characters to be equal.
Kana sensitive—Forces SQL Server 2000 to evaluate the difference between the two Japanese character sets (Hiragana and Katakana). If Kana sensitive is not selected, SQL Server 2000 considers the Hiragana and Katakana character sets to be equal.
Width sensitive—Forces SQL Server 2000 to evaluate the difference between a single-byte (half-width) character and its corresponding double-byte (full- width) character. If Width sensitive is not selected, SQL Server 2000 considers the single-byte and double-byte characters to be equal.
I suggest that you specify the Binary Sort order option for your installation, but only if you do not need to specify that the Collation Setting be compatible with earlier versions of SQL Server (keep reading). Although this sometimes might not sort in the order you expect, it is much faster, and performance is an essential ingredient of a good database.
The final option in this screen is the SQL Collations option. As the screen specifies, this option is used for compatibility with previous versions of SQL Server, including versions 7.0, 6.5, and earlier. Select this option only if the installation will communicate with installations of earlier versions (not required for our SQL Spy Net application).
However, one of the cool new features of SQL Server 2000 is the collation support at a database level. In previous versions of SQL Server, after the collation setting was set, you couldn’t change it without reinstalling. But with SQL Server 2000, you can have your server set to Windows collation, but when you create a database, you can set its collation setting to SQL collation. This takes away the mind-reading capabilities you used to need when performing your installations. Now that’s cool!
When you are happy with the settings, click Next. The next screen (Network Libraries) you see is similar to the previous one.
This screen relates to the Network Libraries you want to install for SQL Server 2000 to communicate between client and server. For a more thorough discussion of how client/server architecture fits in with these options.
The Network Libraries are the communication protocols that SQL Server 2000 uses to communicate on various networks. The protocols enable SQL Server 2000 to communicate by allowing packets to travel between the SQL Service and the PCs with which it is communicating.
Packets are small bits of data grouped together to be sent as one item. This is analogous to putting an invoice and an advertising flyer in an envelope and forwarding the package to your customer.
A SQL Server 2000 installation can listen on a Network Library only if it has been configured. If multiple network libraries are configured, SQL Server 2000 can listen to all libraries that are configured.
The following options are available for configuring SQL Server 2000’s communication protocols:
- Named Pipes—This option is used for configuring installation on an NT 4.0 or a Windows 2000 operating system only. Windows 95 or 98 do not support this protocol.
- TCP/IP Sockets—By default, this is the Network Library that all configurations of SQL Server 2000 use on the operating system on which it is deployed.
- Multi-Protocol—This protocol is used when you want to combine the network protocols that your organization might have. For example, it is tested and supported for TCP/IP, NWLink, IPX/SPX, and Named Pipes. It enables the use of Windows Authentication on all protocols supported by the Windows NT Remote Procedure Call (RPC) functionality.
- NWLink IPX/SPX—This protocol is used when you are deploying SQL Server 2000 on a Novell Network. This enables the Novell SPX client computers to connect and communicate with SQL Server 2000.
- AppleTalk ADSP—This protocol is used when you want Apple Macintosh client computers to connect and communicate with SQL Server 2000 using AppleTalk rather than having to use TCP/IP.
- Banyan VINES—This is another network protocol that is similar to the well- known Novel and NT networks. This communication protocol is specifically for the VINES Network.
Possibly related posts: (automatically generated)
What Happens If I Select the Custom Install Option?
- Microsoft Windows Services for Unix 3.5
- Dedicated Server with Canadian Web Hosting
- Installing and Configuring SQL Server 2000
- Website Hosting Sever, some Pitfalls you need to avoid part 2
- Installing the Application Following the Step-By Step Wizard
- Email Creative Formatting
- Massed head with web hosting?
- Setting Up Your PC as a Web
- User Friendly Web Hosting Basic Guide
- Installing the Application Following the Step-By Step Wizard continue...
- June 5th
Once you have built your web application, the next step is to host or deploy your application to the Internet or intranet so the remote users can access your application via a browser. … Application Development
) 7195 The code produces a list of OPTION tags from an array, array keys being option values and array items being option texts. … Christmas Items
CA ARC serve Backup Agent for Microsoft SQL provides efficient backup and restore of SQL Server 2005 databases, while there in use, by enabling CA ARC serve Backup to send and retrieve data to and from the SQL Server. … CA ARCserve Backup Agent
If you do not wish to be bound by a revision or modification to any Registry policy, your sole remedy is to cancel your domain name registration by following the appropriate Registry policy regarding such cancellation. … Domain Registration
Corporate Casuals supplies custom embroidered and printed apparel direct to small businesses and organizations. … Custom Embroidered Shirts