Help and Support
 

powered byLive Search

PRB: Cannot Specify Instance Name Using SQL Server 2000 Merge Modules

Retired KB ArticleThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
View products that this article applies to.
Article ID:281983
Last Review:October 26, 2007
Revision:1.1
This article was previously published under Q281983

SYMPTOMS

When using the SQL Server 2000 Desktop Engine merge modules as an integrated part of a custom setup, you may not be able to customize the Microsoft Data Engine (MSDE) installation using the same command-line parameters as with the SQL Server 2000 Desktop Engine install package.

Back to the top

CAUSE

External properties that are exposed by way of the command line in the SQL Server 2000 Desktop Engine install package are not exposed in the SQL Server 2000 MSDE merge modules. This is in order to allow customers using the merge modules to control the way these properties are used. For example, you may not want to allow the SQL instance name to be changed from the command line; rather, you may wish to author a specific instance name in the Property table of your custom install package.

Back to the top

RESOLUTION

The setup author could add an entry to the Property table by using a Windows Installer database editing tool such as Orca.exe to assign the specific internal properties used in the SQL Server 2000 MSDE merge modules to a specific value. For example, to set the instance name to be used, you would add an entry to the Property table and assign the SqlInstanceName property a specific value.

The following internal properties are used by the SQL Server 2000 MSDE merge modules and can be set in this manner. The corresponding external properties are listed for reference; however, they are available only in the SQL Server 2000 Desktop Engine install package, not the SQL Server 2000 MSDE merge modules.

External PropertyInternal Property
CALLBACKSqlCallback
COLLATIONSqlCollation
DATADIRSqlDataDir
TARGETDIRSqlProgramDir
INSTANCENAMESqlInstanceName
SECURITYMODESqlSecurityMode
UPGRADESqlUpgrade
UPGRADEUSERSqlUpgradeUser

Some of the above properties must be specific values. The value of SECURITYMODE or SqlSecurityMode should be SQL in order to allow SQL Server authentication. For upgrading, UPGRADE or SqlUpgrade should be 1, and UPGRADEUSER or SqlUpgradeUser should be SA.

Back to the top

STATUS

This behavior is by design.

Back to the top

REFERENCES

255905 (http://support.microsoft.com/kb/255905/EN-US/) HOWTO: Use Orca to Edit Windows Installer Files

Back to the top

APPLIES TO
•Microsoft SQL Server 2000 Desktop Engine (Windows)

Back to the top

Keywords: 
kbproductlink kbprb KB281983

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by E-mail, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.