[MSSQL] msde2000 Installation Details

Source: Internet
Author: User
Tags strong password

MSDE is a desktop SQL service engine provided by Ms. It is a simplified version of SQL Server and has most common functions of SQL Server. It is more stable and powerful than access, and requires less capacity and resources than SQL Server. MSDE provides a simpler solution for small databases.

I tried to install MSDE before and encountered many problems. This is especially true when MSDE 2000 release a (fixed the Slammer Worm vulnerability) is installed. (The MSDE of the Office 2000 series is not release a and will not encounter this problem, but the updated version should be used for security consideration .)

The MSDE 2000 installation file contains many switches and parameters. The SA strong password requirements mentioned above are also set through parameter:

The setup.exe switches are:/?,/I,/Settings,/L * V,/Upgradesp,/Qn,/Qb, And/X.

The setup.exe parameters are:Allowxdbchaining,Blanksapwd, callback, Collation,Datadir,Disablenetworkprotocols,InstanceName,Sapwd,Securitymode,Targetdir,Upgrade,Upgradeuser, AndUpgradepwd.

Syntax

Setup[/?]

[

[/I Package_file --Specify the installation package (. MSI) (sqlrun01.msi through sqlrun16.msi)

[/SettingsIni_file] -- Specify the configuration file (. INI)

| [[Allowxdbchaining = 1]

[Blanksapwd = 1]

[Callback=Dllname!Callbackfunctionname]

[Collation="Collation_name"]

[Datadir="Data_folder_path"]

[Disablenetworkprotocols=N]

[InstanceName="Instance_name"]

[Sapwd="Sa_password"]

[Securitymode=SQL]

[Targetdir="Executable_folder_path"]

[Upgrade=1]

[Upgradeuser=Admin_login]

[Upgradepwd=Admin_password ]

]

]

[/L * V[Filename]

[/Upgradesp{Sqlrun

| <Msipath>SqlrunNn. MSI }

]

[/Qn|/Qb]

[/X Package_name]

]

 

Note:

Allowxdbchaining = 1

In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default behavior of the installer and enables cross database ownership chains for the instance. for more information about cross database chaining, see cross dB ownership chaining. you shoshould not use this parameter unless you are running an application that requires cross database ownership chains.

Blanksapwd = 1

Overrides the installer's default behavior, which is to require that you specify a strongSAPassword. If you specifyBlanksapwd = 1, The installer assigns a null password toSALogin

 

Security noteAssigning a null, blank, simple, or well-known password toSALogin can allow unauthorized people access to your data.

 

Callback =Dllname!Callbackfunctionname

Specifies the name of the DLL containing the Desktop Engine Windows Installer callback function, and the name of the callback function. For more information, see Windows Installer Callback Functions for Desktop Engine.

Collation ="Collation_name"

Specifies the SQL Server collation that will be used as the default collation for this instance of the Desktop Engine. For information about collation names, see Windows Collation Name and SQL Collation Name.

Datadir ="Data_folder_path"

Specifies the folder where the SQL Server system databases are built. Assuming that the system default for program files is C: \ Program Files:

  • The default value for default instances is: C: \ Program Files \ Microsoft SQL Server \ MSSQL \ data \.

  • The default value for named instances is c: \ Program Files \ Microsoft SQL Server \ MSSQL $<Instance_name>\ Data \, whereInstance_nameIs the name specified in the INSTANCENAME option.

    The file path for this parameter must end with a backslash (\). when installing a default instance, setup appends mssql \ data to the end of the path specified in DATADIR. when installing a named instance, setup appends mssql $ <Instance_name>\ Data, whereInstance_nameIs the value specified in the INSTANCENAME option.

    Setup builds two other folders at the same location as the Data folder, a Log folder for the database engine error logs, and an Install folder containing installation scripts.

 

NoteSettings that contain spaces shoshould be enclosed with quotation marks.

INSTANCENAME="Instance_name"

Specifies the name for the instance. If no instance name is specified, the instance is installed as a default instance.

SAPWD="Sa_password"

Specifies the password to be assigned toSaLogin when installing a new instance of MSDE 2000.SAPWDIs ignored when you upgrade an existing instance of MSDE 2000, so you shoshould ensureSaLogin has a strong password before upgrading. You shoshould always specify a strongSaPassword, even when using Windows Authentication Mode. WhileSAPWDParameter is not written to the installation log file when running Setup.exe, it is if you install using merge modules.

SECURITYMODE=SQL

Specifies that the instance be configured in Mixed Mode, where the instance supports both SQL Server Authentication and Windows Authentication connections.

In Microsoft Windows NT 4.0 or Windows 2000, ifSECURITYMODE=SQLIs not specified, the instance will be configured in Windows Authentication Mode. The instance will only support Windows Authentication connections, and the Windows local administrator's group will be added to the SQL ServerSysadminRole. IfSECURITYMODE=SQLIs specified, Setup configures the instance in Mixed Mode.

 

Security NoteWhen possible, use Windows Authentication.

 

In Microsoft Windows 98 or Windows ME, the instance is always configured to use Mixed Mode, regardless of whetherSECURITYMODE=SQLIs specified. On these operating systems, MSDE 2000 can only support SQL Server Authentication connections.

TARGETDIR ="Executable_folder_path"

Specifies the folder where the Desktop Engine executable files are to be installed. Assuming that your system default for program files is C: \ Program Files:

  • The default value for default instances is: C: \ Program Files \ Microsoft SQL Server \ MSSQL \ Binn \.

  • The default value for named instances is: C: \ Program Files \ Microsoft SQL Server \ MSSQL $<Instance_name>\ Binn \ for named instances, whereInstance_nameIs the name specified in the InstanceName option.

    The file path for this parameter must end with a backslash (\). when installing a default instance, setup appends mssql \ binn to the end of the path specified in TARGETDIR. when installing a named instance, setup appends mssql $ <Instance_name>\ Binn.

 

NoteSettings that contain spaces shoshould be enclosed with quotation marks.

 

Upgrade=1

Specifies that Desktop Engine Setup or Windows Installer is upgrading an instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000 Desktop Engine. the only value supported is 1. MSDE 1.0 operates in the same fashion as a default instance of MSDE 2000, and is always upgraded to a default instance of MSDE 2000.

Upgradeuser=Admin_login

Specifies the login to be used when you upgrade an instance of either MSDE 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a member ofSysAdminFixed server role. This parameter is only used when you specify SECURITYMODE = SQL when upgrading an instance of MSDE.

Upgradepwd=Admin_password

Specifies the password for the login specified inUpgradeuserWhen you upgrade Desktop Engine using SQL Server Authentication.

/L * V[Filename]

Specifies that a verbose log be created. IfFilenameIs specified, the log is stored in the file specified.

My personal summary: I was always prompted to set up sapwd before installation, so I wrote sapwd = SA at will. As a result, after installation, the database could not use SA for login. WriteBlanksapwd = 1This situation can be avoided. (SAS still uses a blank password, which is not secure)

Two points are also described here:

  1. SECURITYMODE=SQLWhen MSDE is installed on an operating system (NT, 2000, XP, 2003) based on the NT kernel identity authentication, the default authentication mode is Windows Authentication mode ), the system administrator account will automatically become SQL SysAdmin. After setting this parameter, you can use the hybrid mode to log on.
  2. DATADIR, TARGETDIRThe storage locations of data and SQL executable files are respectively.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.