Tuesday, May 10, 2011

Creating a new instance of SQL Server

i am just divided the installation of sql server 2005 into steps and posted here. actually there is only one difference in fresh installation of sql server and creating an other instance on a server having sql server running on it. if you want to create a second instance on the server step five is the key. all the remaining part remains the same.

first step:

The first step in installing the sql server 2005 is, of  course , to launch the installers main window (or splash screen). You do it by inserting the install dvd in the drive. If you explore the dvd and click on setup.exe the start screen is skipped and you directly jump to install program.

In the splash screen you will see the following options

  1. Requirement documentation,
  2. License agreement,
  3. Release notes,
  4. Web links,
  5. Installation of sql server 2005,
  6. Upgrade of sql server from previous versions and
  7. The new sql native client.

On the start screen, under install, click the server components, tools, books online, and sample links.

The next screen takes you to the component update phase of the install, during which some of the requisite software items must be installed.
  •  The .net framework 2.0(it is required because sql server 2005 is a common language runtime host, allowing   developers to write managed code executed in a t-sql. It is also required in many more components as every thing is built on .net in the sql server 2005)
  •  Sql server native client.
  •  Sql server setup support files used by the installer.

If all goes well upon completion of this phase, click the next button in the screen.

After which installation wizard is launched. Click next and install application invokes the SCC (System Configuration Checker).

The SCC’s job is to ensure that every aspect of the sql server 2005 compatibility is met, including the following.

  • Operating system (including word-length [32-bit and 64-bit]) and service pack compatibility
  •  Installed service (particularly WMI) and other software compatibility (including a
  • check for Internet Explorer 6 SP1 or later)
  •  Whether the logged-in user is a system administrator (a must)
  •  Whether no other instances of the installer are running and no reboots are pending from other installers
  •  Whether the destination drive is formatted, writable, and uncompressed

SCC scans the environment, checking compatibility and also for previous editions of related software, such as MSXML (which happens to be upgraded to version 6 during the install) and previous editions of SQL Server. SCC also builds a list of available features, based on these results. 

When the SCC scan is complete, you can click the Report button to view or save its detailed report, which notes any issues and offers suggestions for their resolution. There are several scenarios where the list of available features is affected by the results of SCC’s scan. 

For example: IIS might not be set up on the target machine. A warning is indicated in SCC’s results grid, and later, when we reach the Components to Install screen (which presents the list of available features) the Reporting Services (SSRS) check box will be disabled because SSRS depends on IIS. 

third step:

When you have resolved any issues on your system, you click the Next button, launching the third phase of the install. At this point, you enter your personal name, company name, and security key data (this key is auto-entered for MSDN subscription–licensed versions of SQL Server 2005).

fourth step:

after entering the license details press next and now the sql server installation part begins.

components to install screen. 

The following are the most commonly available features:

  •  Database services—Including the database engine and shared tools (discussed in multiple chapters), replication  and Full-Text Search.
  •  Analysis Services—Including the engine used to create business intelligence solutions that rely on OLAP and data mining.
  •  Reporting Services—Including the engine and tools used to generate and deploy data-centric reports.
  •  Integration Services (SSIS)—Including the engine and tools for performing data import/export/transfer with (or without) transformation.
  •  Notification Services—Including a framework (based on the publisher/subscriber paradigm) for providing notifications when specific events occur. Note that Notification Services also provides the backbone for Service Broker .
  •  Client Components—Including all the new connectivity, development, and server management tools.

If you click the Advanced button at the bottom right of the screen, you can customize your installation by choosing from several sub features.

The Feature Selection screen illustrates that installation is now completely component based. This means that each component is actually installed from its own MSI package and can be configured and removed separately from others. In addition, multiple instances of each component can be installed separately. This means, for example, that you can have five named instances of Analysis Server, two named instances of the database engine, three named instances of Reporting Services, and so on. It’s completely up to you.

Now that you’ve made your selections, click Next. 

fifth step:

At the Instance Name screen, you can install SQL Server 2005 as the default instance (if a SQL Server 2000 or 7 default instance is not present) or as a new named instance. Only one default instance of any version of SQL Server is possible on a given server.

The verbiage on this screen is somewhat opaque. 
Basically, it attempts to convey the following information:

  •  If a previous edition of SQL Server is currently installed (such as SQL Server 2000) and the Default Instance radio button is selected, that previous edition will be upgraded to SQL Server 2005.
  •  If a previous edition of SQL Server is currently installed (such as SQL Server 2000) and the Default Instance radio button is not selected, that previous edition will be left alone, and you must provide a name for your new instance of SQL Server 2005 in the text box. The default instance on the server will remain a SQL Server 2000 instance.
  •  If Default Instance is selected and no previous edition of SQL Server is currently installed, the default instance of SQL Server 2005 is installed (no previous instance means no upgrade).

When installing a new named instance on a server that houses multiple SQL Server versions, it’s a good idea to name the new instance something similar to SQLversion. 
here version means like 05/08 for 2005 or 2008 servers respectively..

This helps to alleviate any confusion among clients as to which version of SQL they are connecting to. In addition, it’s a good idea to change the TCP/IP port used to reach this new instance to a fixed port number (other than 1433). (SQL Server uses a range of dynamic port numbers by default.)

You can also view a list of currently installed instances, either of SQL Server or Analysis Services, by clicking the Installed Instances button at the bottom right of the screen.

 Note again that SQL Server 2000 instances will be reported as version 8.n. 

If this not your first install of SQL Server 2005 on the destination machine, the next dialog is Existing Components, which exists merely to tell you that some of the components already installed (such as SMSS and SQL Browser), will not be installed again because only one instance of each is needed.

Click Next, and you reach the Service Account screen 

sixth step:

which requires you to specify the user accounts under which the various SQL Server services
will run.

One recommendation is to create a single local or domain account for dedicated SQL Server 2005 use and assign it to all services or, for finer-grained control, create multiple accounts, one for each service. This helps reinforce the least-privileged user account approach, which states that a user should have only the privileges required to get the job done—and no more. It also makes it clearer for network administrators as to when SQL Server services (as opposed to the multitude of other running services) are requesting access to a resource. And, in some scenarios, the Local system or Network service accounts may be endowed with more privileges than desirable since they are shared. Also on the Service Account screen, you can select to start various SQL Server services after install by checking the check boxes at the screen bottom. It is highly recommended to auto-start both the SQL Server and SQL Browser services, as they represent the database engine and the service that makes it accessible (via network name resolution), respectively. (You can change auto-start later, using the SQL Server Configuration Manager.) Make your selections and click Next.

The SQL Server Browser service is installed only once, no matter how many instances
you install.

seventh step:

The following screen (Authentication Mode) provides the authentication options for SQL Server (Windows-only or mixed-mode).

Note that mixed-mode authentication is required for any feature where in non-Windows clients will be authenticating to SQL Server 2005. A strong sa password is recommended. Note also that if you select Windows authentication, the sa password is randomly generated. You can change it using SMSS after the install (recommended).

Click Next, and the Collation Settings screen appears. 

eighth step:

where you can set the collation for each SQL Server service.

Collations are important because they are used to determine case-sensitivity of textual data for comparisons, sort order in indexes, and so on.

You can create and customize your own collation by clicking the Collation Designator and Sort Order radio button and then checking the desired collation options.

If you’re running Windows in the United States, the collation selection defaults to the SQL Server collation (Dictionary Order, Case-Insensitive, for use with 1252 Character Set), and this is a fine choice.

To achieve the same collation when designating your own collation, select the Collation Designator and Sort Order radio button, select Latin1_General from the drop-down box, and then check the Accent - Sensitive check box. (This is also the collation compatible when you’re doing string comparisons using SQL code developed in .NET [that is, SQLCLR code]).
An excellent Books Online topic that discusses the many considerations when choosing a collation is titled Using SQL Collations.

If you’ve chosen to install Reporting Services, clicking Next takes you to the Report Server screen .

ninth step:

 which has one related option: Install and configure (Install the Default Configuration) or just install

If you choose to install and configure, the Details button is enabled. Clicking Details shows the database, virtual directory, and SSL settings that SQL Server will use by default.

Click Next to reach the Error and Usage Report Settings screen.

tenth step:

Here, you have the option to send error and feature usage data to Microsoft headquarters. This process is colloquially known as “phoning home,” and you may be inclined to keep both options unchecked.

Note that doing so reduces Microsoft’s ability to gather important statistics helpful when debugging for the next service pack release.

eleventh step:

The final screen (Ready to Install) provides a summary of your chosen install options and the Finished button you’ve been waiting to press.

do comment....

No comments:

Post a Comment