solving sql server problems for millions of dbas and developers since 2006



SQL Server DBA Tips SQL Server Developer Tips SQL Server Business Intelligence Tips SQL Server Career Tips SQL Server Tip Categories SQL Server Tutorials SQL Server Webcasts SQL Server Whitepapers SQL Server Tools SQL Server Questions and Answers MSSQLTips Authors About MSSQLTips SQL Server User Groups MSSLQTips Giveaways MSSQLTips Advertising Options

MSSQLTips Facebook Page MSSQLTips LinkedIn Page MSSQLTips RSS Feed MSSQLTips Twitter Page MSSQLTips Google+ Page





SQL Product Highlight

Devart - dbForge SQL Complete

dbForge SQL Complete is a code autocomplete tool for SQL Server Management Studio and Visual Studio. Free and advanced paid editions of this useful add-in offer powerful autocompletion and formatting of T-SQL code that replaces native Microsoft T-SQL Intellisense.

Learn more!




SQL Server 2000 Unattended Installation

By: | Read Comments (1) | Print

Edgewood Solutions is a technology company focused on Microsoft SQL Server and founder of MSSQLTips.com.

Related Tips: More

Problem
SQL Server 2000 installations are tedious and time-consuming, particularly if there are many servers to roll out. Having someone sit in front of the server during installation can also be very expensive. Microsoft created a method through which SQL Server can be installed in an unattended fashion. Using an unattended installation method can provide consistent server installations throughout the organization, and reduce the Total Cost of Ownership (TCO) of the database system.

Solution
The heart of SQL unattended installation is the .ISS file, which is a file that holds the component configuration information for the SQL installation. Different .ISS files can be created, based on different configurations of SQL Servers in the organization. Microsoft provided some of these files on the main section of the CD for common installations:

  • sqlins.iss: Used to install typical server components of SQL Server
  • sqlcli.iss: Used to install connectivity and management tools but no server components
  • sqlcst.iss: Used to install all components of SQL Server
You can customize the installation process and create an .ISS file from either the network share of the installation files or the CD/DVD by running the SQL Server 2000 installation and choosing Advanced Options:

The Advanced Options choice in SQL Server 2000 Installation

When you choose the Advanced Options radio button another screen will appear. This is where you choose to Record an Unattended .ISS file:

Choose Record An Unattended .ISS file

Once you have finished specifying the components to install, a screen will appear letting you know that the installation process has collected what it needs to write the .ISS file. This file will be written to the %system_root% folder of the computer the installation was run on (i.e., C:\Windows\):

Screen to signify installation has enough information to write .ISS file

Much like unattended installation for Windows Server products, a batch file can be written to run the installation and specify the .ISS file to be used. The batch file, in turn, can be rrun as a scheduled task or whenever convenient. The command line syntax for starting the installation is:
"folder_location"\x86\Setup\SetupSQL.exe

There are also switches to specify various options for the installation process:

  • -S: Runs the installation in silent mode without dialog boxes
  • -F1: Specifies the .ISS file to be used for the installation
  • -SMS: When used in conjunction with the start /wait command, it returns control to the command prompt once installation is complete

Here is an example of the command line syntax:

Example of command line syntax for SQL unattended installation

Part of the installation process asks for an SA password as well as service account username and password information. Although this information is stored in the .ISS file, the passwords are encrypted so that passwords aren't compromised. When creating a network share for the installation files, make sure the account used to run the batch file (whether through Scheduled Task or other mechanism) has adequate permissions to access the network share that houses both the installation files and .ISS files. Avoid the use of mapped drives in the batch file and use UNC paths if needed.

Next Steps

  • Whether rolling out a series of new SQL Servers or eventually rolling out additional servers, consider the use of unattended installation to provide more consistent installations, make better use of personnel, and reduce the Total Cost Ownership (TCO) of a SQL Server 2000 database infrastructure
  • Review the information on Performing an Unattended Installation
  • Refer to MSSQLTIPS for more information on SQL Server 2000 and 2005


Related Tips: More | Become a paid author


Last Update: 10/19/2006

Share: Share 






Comments and Feedback:

Wednesday, February 15, 2012 - 3:19:34 AM - Khalid Ahmed Read The Tip
I need Some help About this process please contact me at amalierpk@gmail.com


Post a Comment or Question

Keep it clean and stay on the subject or we may delete your comment.
Your email address is not published. Required fields are marked with an asterisk (*)

*Name   *Email   Notify for updates
Comments
*Enter Code refresh code


 
Sponsor Information
"SQL doctor ROCKS! As soon as I ran it, problems that have been giving me headaches were identified and cured."

Time-strapped database professionals use SQL Monitor to look after their servers. Try it online.

What grade do you think your SQL Servers get? Find out with Edgewood's SQL Server Health Check starting at $995.

Get SQL Server Tips Straight from Kevin Kline.

Join the over million SQL Server Professionals who get their issues resolved daily.

Learn SQL Server 2012, Performance Tuning, Development, Administration, Replication and more - free webcasts


Copyright (c) 2006-2012 Edgewood Solutions, LLC All rights reserved
privacy | disclaimer | copyright | advertise | about
authors | contribute | feedback | giveaways | user groups
Some names and products listed are the registered trademarks of their respective owners.


Edgewood Solutions LLC | MSSharePointTips.com | MSSQLTips.com