sql server msde:
I am looking for a resource online or a document that lists all of the possible options that can be placed in the setup.ini file. Does anyone possibly have this information or know where I can find it?
3.4.3 MSDE 2000 Setup Parameters MSDE 2000 is designed to be distributed with applications and installed by the setup program of the application. The Desktop Engine Setup.exe utility is usually called by an application setup utility, but can also be run from a command prompt window. The MSDE 2000 setup utility does not have a graphical user interface. Instead, this utility accepts a set of switches and parameters that specify the actions the utility should take. You can only use MSDE 2000 Release A to install new instances of MSDE 2000. Do not use it to upgrade instances running earlier versions of MSDE 2000. When running the MSDE 2000 Release A version of Desktop Engine Setup.exe, do not use these switches or parameters: UPGRADE, UPGRADEUSER, UPGRADEPWD, or /upgradesp. Use SQL Server 2000 SP3a to upgrade existing instances of MSDE 2000 to MSDE 2000 SP3a. For more information about upgrades, see 1.0 Introduction. This readme only discusses the more commonly used Setup parameters and switches. All of the switches and parameters supported by Desktop Engine Setup.exe are documented in "Customizing Desktop Engine Setup.exe" in SQL Server 2000 Books Online. The version of this topic that describes the behavior of Desktop Engine Setup.exe included in MSDE 2000 Release A is at this Microsoft Web page. For more information about setup documentation, see 1.1 MSDE 2000 Documentation. You must enclose the values for MSDE Setup parameters in double quotation marks if the values specified have special characters, such as blanks. Otherwise quotation marks are optional. Most installations of MSDE 2000 Release A are made using only these Setup parameters: Parameter Description SAPWD="AStrongPassword" Specifies a strong password to be assigned to the sa administrator login. INSTANCENAME="InstanceName" Specifies the name of the instance. If INSTANCENAME is not specified, Setup installs a default instance. Other parameters often used to tailor an installation are: Parameter Description DISABLENETWORKPROTOCOLS=n Specifies whether the instance will accept network connections from applications running on other computers. By default, or if you specify DISABLENTWORKPROTOCOL=1, Setup configures the instance to not accept network connections. Specify DISABLENETWORKPROTOCOLS=0 to enable network connections. SECURITYMODE=SQL Specifies that the instance be installed in Mixed Mode, where the instance supports both Windows Authentication and SQL Authentication logins. DATADIR="data_folder_path" Specifies the folder where Setup installs the system databases, error logs, and installation scripts. The value specified for data_folder_path must end with a backslash (\). For a default instance, Setup appends MSSQL\ to the value specified. For a named instance, Setup appends MSSQL$InstanceName\, where InstanceName is the value specified with the INSTANCENAME parameter. Setup builds three folders at the specified location: a Data folder, a Log folder, and a Script folder. TARGETDIR="executable_folder_path" Specifies the folder where Setup installs the MSDE 2000 executable files. The value specified for executable_folder_path must end with a backslash (\). For a default instance, Setup appends MSSQL\Binn to the value specified. For a named instance, Setup appends MSSQL$InstanceName\Binn, where InstanceName is the value specified with the INSTANCENAME parameter. When you use DISABLENETWORKPROTOCOLS=0 to enable network support for an instance of MSDE 2000, applications connecting to the instance over a network use Microsoft Data Access Components (MDAC). All versions of Windows supported for use with MSDE 2000 include a version of the MDAC software that works with MSDE 2000 Release A. For more information about network communications, see this Microsoft Web page. Using an .ini File Desktop Engine Setup.exe parameters can be specified in two locations: On the command prompt when running Setup.exe. In an .ini file whose location is specified by a /settings switch. An ..ini file is a text file, such as a file created using Notepad, and saved with a file name that has an extension of .ini. In the .ini file, the first line is [Options], and then the parameters are specified, one parameter per line. Important If you use an .ini file during setup, avoid storing security credentials in it. This example specifies the parameters on the command prompt: setup SAPWD="AStrongPassword" INSTANCENAME="InstanceName" TARGETDIR="C:\MyInstanceFolder" To run Setup with the same parameters using an .ini file, use Notepad to create a file named MyParameters.ini with these contents: [Options] INSTANCENAME="InstanceName" TARGETDIR="C:\MyInstanceFolder" Then run Setup using the /settings switch to point to the .ini file: setup /settings "MyParameters.ini" SAPWD="AStrongPassword" Requesting a Setup Log You will need a verbose log to verify that the installation succeeded or to assist in debugging any problems that occur. To generate a verbose log, specify /L*v <LogFileName>. <LogFileName> is the name of a log file where Setup will record all of its actions. If you do not specify a path as part of the name, the log file is created in the current folder. If you are executing Setup from a compact disc, you must specify the full path to a folder on the hard disk of your computer. This example creates a log file, MSDELog.log, in the root folder of the C: drive: setup SAPWD="AStrongSAPassword" /L*v C:/MSDELog.log If installation succeeds, an entry similar to the following will be at the end of the log: === Logging stopped: 5/16/03 0:06:10 === MSI (s) (BC:7C): Product: Microsoft SQL Server Desktop Engine -- Installation operation completed successfully. If the installation does not succeed, an entry similar to the following will be at the end of the log: === Logging stopped: 5/15/03 23:50:34 === MSI (c) (6A:CE): Product: Microsoft SQL Server Desktop Engine -- Installation operation failed. If the installation failed, search for the string "value 3" in the error log. Within 10 lines of the string will be a failure notice for a custom action. The notice will have additional information about the nature of the failure. [Top] -----Original Message----- From: Scott [mailto:sts@weiland-wfg.com] Posted At: Wednesday, 19 January 2005 8:19 AM Posted To: microsoft.public.sqlserver.msde Conversation: List of options for the .ini file Subject: List of options for the .ini file I am looking for a resource online or a document that lists all of the possible options that can be placed in the setup.ini file. Does anyone possibly have this information or know where I can find it? Thank you very much!
Don't see what you're looking for? Try a search.
|