Re: Setup of SQLExpess Options

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for your followup Matt,

Regarding on your recap on the requests, here is a simple summary on the
current available solutions:

Need hints for command line params - specificaly:
====================
this should be configurable through the <command> element in the
Package.xml file(of vs 2005 bootstrapper package). You can find that the
built-in SQL Express bootstrapper package's package.xml already has
specified some commandline arguments. You can refer to its syntax(or the
custom VS 2005 bootstrapper package article)


Allow tcp/ip access
==================================
The [DISABLENETWORKPROTOCOLS] parameter is used for setting the startup
type of the network protocols. It has the following 3 options:

0 - Shared memory = On, Named Pipes = On, TCP/IP = On

1 - Shared memory = On, Named Pipes = Off (local only), TCP/IP = Off

2 - Shared memory = On, Named Pipes = Off (local only), TCP/IP = On




Specify instance name (actually already have this one from existing
package.xml)
==============================
there is a "[Instancename] parameter you've already found.



Set security to be SQL only
===============================
there is a [SECURITYMODE] parameter you can use for the sqlexpress's setup
program.


You can find all the available command parameters in the following BOL
reference(it is for standard SQL Server 2005, so there has some parameters
not workable for SQL express)

#How to: Install SQL Server 2005 from the Command Prompt
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#installationscripts




Also need hints for how to handle an installcondition of my instance of SQL
Express is installed.
====================================
I think this can be done through VS 2005 bootstrapper package's "Install
Check" and "Install condition" feature(mentioned in the "Authoring custom
bootstrapper package...." article). And for your scenario, if you want to
detect whether there is already an named SQL instance(with the same name as
the one you want to install), you can check the registry for such a subkey.
And the VS 2005 bootstrapper package's "Install Check" contains
"RegistryCheck" by which you can let your bootstrapper installation run
depend on some registry value.

#<InstallChecks> Element (ClickOnce Bootstrapper)
http://msdn2.microsoft.com/en-us/library/ms229432.aspx


Hope the above helps clarify it further.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • RE: SBS Sp1 Sharepoint websites doesnt work anymore
    ... Microsoft OLE DB Provider for SQL Server ... main install. ... CSuiteHelpComponentRoot::isSharePointUsingWMSDE The sql command is: SELECT ...
    (microsoft.public.windows.server.sbs)
  • Re: Location of Data
    ... > first install), then you will probably reach a point on your second or third ... > Users Shared Folders (command line) ... > Sharepoint Databases ... >> True I can arrange that, but I was more worried about the SQL data filling ...
    (microsoft.public.windows.server.sbs)
  • Re: MSBuild bootstrapper issue with Sql Server Express
    ... Server Express SP-2 install in the bootstrapper. ... Sql Server Express SP2 bootstrapper? ... We are using the bootstrapper command in MSBuild to install Sql Server ...
    (microsoft.public.vstudio.general)
  • Re: SBS2003 Std & SQL
    ... The command line I used to install MSDE2000a ... you would need SQL 2000 Standard Edition ... >full-blown SQL, either by upgrading to SBS 2003 Premium, ...
    (microsoft.public.windows.server.sbs)
  • Re: 2005 Full Text Error
    ... I did have problems with the install. ... I couldn't install using the GUI, ... command line) after the original install. ... So I tried the install again with just SQL and FT from command line - it ...
    (microsoft.public.sqlserver.fulltext)