Home > Articles > Data > SQL Server

  • Print
  • + Share This
Like this article? We recommend

Checking for the Existence of Our Variables

Once again, we check the presence of each of our variables that we reference. I have provided you with a sample statement for the check of the CompanyName variable (see Listing 2). By now, I am sure that you will be more than comfortable writing the statements (or copying most of them from the InstallSQLServer.bat script) to check for the existence of the other variables.

Listing 2—Checking for the Existence of the Variables.

if not "%CompanyName%"=="" goto :CompanyNameOK
    (echo ERROR: Missing input parameter CompanyName.)
    (echo ERROR: Missing input parameter CompanyName.) >> %Logfile%
    set RETVAL=10
    goto :end

...other parameter checking statements to follow...


Just be a little careful when you aren't too strict about the parameters that you expect. For example, although we have specified that some parameters are optional in this script, you should still check for them. If they aren't supplied, you should assign a default value rather than error out the script.

For example, see the following snippet of code for the checking of the SQLsaPwd parameter:

     if "%NTAuthentication:~0,1%"=="Y" goto :UseNTAuthentication
        if not "%SQLsapwd%"=="" goto :SQLsapwdOK
           (echo ERROR: Missing input parameter SQLsapwd.)
           (echo ERROR: Missing input parameter SQLsapwd.) >> %Logfile%
           set RETVAL=15
           goto :end

The SQLsaPwd parameter is required only if the NTAuthentication variable is set to "No". In this instance, it wouldn't make sense to error out the script if the SQLsaPwd parameter were not supplied.

After we have ensured that the user of our script has provided all of the parameters, we can then generate the .iss file for the installation of SQL Server 2000 SP2. This is a very similar process to creating the .iss file for the installation of SQL Server. Note, however, that this .iss file (for SP2) is a lot less complex than it is for the installation of SQL Server. Most of the hard work is done by the time an installation of an SP is required, so the .iss file does not require as much detail about your specific SQL Server installation.

Listing 3 shows the code and the sections of the .iss file that we will generate.

Listing 3—Writing Out the .iss File to Install SP2.

    set ISSFile=%ISSDir%\SQL2KSP2.iss
    REM Build the auto-answer file for the setup program.

    (echo Building auto-answer file.) 
    (echo Building auto-answer file.)	>> %LogFile%

    (echo [InstallShield Silent])     > %ISSFile%
    (echo Version=v5.00.000)       >> %ISSFile%
    (echo File=Response File)       >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [File Transfer])        >> %ISSFile%
    (echo OverwriteReadOnly=NoToAll)   >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgOrder])           >> %ISSFile%
    (echo Dlg0=DlgW2kReboot-0)      >> %ISSFile%
    (echo Count=13)            >> %ISSFile%
    (echo Dlg1=SdWelcome-0)        >> %ISSFile%
    (echo Dlg2=DlgMachine-0)       >> %ISSFile%
    (echo Dlg3=DlgInstallMode-0)     >> %ISSFile%
    (echo Dlg4=SdLicense-0)        >> %ISSFile%
    (echo Dlg5=DlgInstanceName-0)     >> %ISSFile%
    (echo Dlg6=DlgMaintainInstall-0)   >> %ISSFile%
    (echo Dlg7=DlgUpgrade-0)       >> %ISSFile%
    (echo Dlg8=ServerConnect-0)      >> %ISSFile%
    (echo Dlg9=DlgCollation-0)      >> %ISSFile%
    (echo Dlg10=DlgServerNetwork-0)    >> %ISSFile%
    (echo Dlg11=SdStartCopy-0)      >> %ISSFile%
    (echo Dlg12=SdFinishReboot-0)     >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgW2kReboot-0])        >> %ISSFile%
    (echo Result=189)           >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [SdWelcome-0])         >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgMachine-0])         >> %ISSFile%
    (echo Type=1)             >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgInstallMode-0])       >> %ISSFile%
    (echo Type=2)             >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [SdLicense-0])         >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgInstanceName-0])      >> %ISSFile%
    (echo InstanceName=%InstanceName%)  >> %ISSFile%
    (echo Result=0)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgMaintainInstall-0])     >> %ISSFile%
    (echo Type=12)            >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgUpgrade-0])         >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [ServerConnect-0])       >> %IISFile%
    if "%NTAuthentication:~0,1%"=="Y" (
        (echo NTAuthentication=1)   >> %IISFile%
        (echo SQLAuthentication=0)  >> %IISFile%
    ) else (
        (echo NTAuthentication=0)   >> %IISFile%
        (echo SQLAuthentication=1)  >> %IISFile%
        (echo svPassword=%SQLsapwd%) >> %IISFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgCollation-0])        >> %ISSFile%
    (echo collation_name=%SQLCollation%) >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [DlgServerNetwork-0])      >> %ISSFile%
    (echo NetworkLibs=255)        >> %ISSFile%
    (echo TCPPort=%TCPPort%)       >> %ISSFile%
    (echo TCPPrxy=Default)        >> %ISSFile%
    (echo NMPPipeName=\\.\pipe\sql\query) >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [SdStartCopy-0])        >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [Application])         >> %ISSFile%
    (echo Name=Microsoft SQL Server)   >> %ISSFile%
    (echo Version=8.00.000)        >> %ISSFile%
    (echo Company=%CompanyName%)     >> %ISSFile%
    (echo Lang=0009)           >> %ISSFile%
    (echo.)                >> %ISSFile%
    (echo [SdFinishReboot-0])       >> %ISSFile%
    (echo Result=1)            >> %ISSFile%
    (echo BootOption=0)          >> %ISSFile%

    REM Copy and rename the auto-answer file for 
    REM the setup program to the Windows directory i.e. C:\WinNT
    (echo Copying answer file to "%WinDir%".)
    (echo Copying answer file to "%WinDir%".) >> %LogFile%
    (copy /A /Y "%ISSFile%" "%WinDir%\setup.iss") >> %LogFile% 2>>&1


You generate an .iss file for an SP the same way you do for a SQL Server installation. In other words, run the installation program with the command-line switches that we explored in the first article in this series.

As you may have noticed, I already replaced the hard-coded values in the .iss file with my parameters (that is, Collation_Name now has a value of %CollationName%).


The NTAuthentication variable that we use in the .iss file simply specifies the way we want to connect to the SQL Server. That is, with SQL Authentication (NTAuthentication=No), which means that we need to supply a valid password for the "sa" account; or with Windows Authentication (NTAuthentication=Yes), which means that the account we are logged on with must have system admin rights in the SQL Instance that we are upgrading.

After the .iss file has been generated, we copy it to the Windows directory and rename the file to setup.iss. At this point, it is a very easy process to ensure that our .iss file contains the information that we want to configure with our install.

Writing the Code to Actually Install SP2Now the fun stuff! We are ready to install our SP. Check out Listing 4.

Listing 4—Calling the Installation Program for SQL Server 2000 SP2.

    REM SP2 requires that the SNMP service is NOT running before installation
    (echo Stopping the SNMP service)
    (echo Stopping the SNMP service.) >> %LogFile%
    (net stop SNMP /y) >> %LogFile% 2>>&1

    REM Installing SQL Server silently specifying the setup.iss file 
    (echo Launching SQL SP2 setup, commands %AppPath%\setupsql.exe -s -m -SMS -f1 
    (echo Launching SQL SP2 setup, commands %AppPath%\setupsql.exe -s -m -SMS -f1 
"%WinDir%\setup.iss".) >> 
    start /wait "%AppPath%\setupsql.exe" -s -SMS -f1 "%WinDir%\setup.iss" 
>> %LogFile% 2>>&1


A requirement of installing SQL Server 2000 SP2 is to ensure that the SNMP service is stopped before installing the SP. If you are modifying this script for other SPs, this is the section that you stop dependant services with. However, be careful of the order in which you stop services; otherwise, errors may be generated. I use the /y switch on the net stop command to automatically stop all dependant services on the SNMP service. (A nice little undocumented feature for you...well, I couldn't find it, at leastJ).

If SNMP is not installed on your machine, you can either comment this line out or ignore the error that will be returned.

There we go. Now that we have launched the installation of SQL Server 2000 SP2, it is a simple case of restarting services, starting with the SQL Server instance, to make sure that everything worked okay. Listing 5 shows you how to restart the services in code.

Listing 5—Restarting the Services to Make Sure Our Installation was Successful.

    REM Make sure the SQL Server service gets started.
    (echo Attempting to start the SQL Server service "%InstanceName%".)
    (echo Attempting to start the SQL Server service "%InstanceName%".) >> %LogFile%
    (net start "%InstanceName%") >> %LogFile% 2>>&1

    REM Set the return value

    (echo Restarting the SNMP service.)
    (echo Restarting the SNMP service.) >> %LogFile%
    (net start SNMP) >> %LogFile% 2>>&1
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020