SQL 2005 Express Syntax Help

[Nicolus]

Hello,

I apologize in that I am a new member and am still having a hard time navigating this site. So if the answer to this question could have been found elsewhere, please be patiant. I am also SOLELY a Windows Admin and the only reason I use SQL is for our BlackBerry Enterprise Server installation. I do not know anything about SQL.

My question is...

In SQL 2000, when a named instance was created, a folder would be created in the SQL Program Files folders called, MSSQL$InstanceName. But it seems that in SQL 2005 however, when a default instance is made it winds up in a folder called MSSQL.1(or 2, or 3, etc.)\MSSQL\etc. etc.

What I need is someone to help me alter the canned SQL template below so that the Instance I am creating winds up looking like C:\Program Files\Microsoft SQL Server\MSSQL$BLACKBERRY instead of C:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL

Thank you.

The canned template is;

[Options]

USERNAME="My Username"
COMPANYNAME="My Company Ltd"

;--------------------------------------------------------------------
; INSTALLSQLDIR specifies the location for the instance specific binary files.
; Default location is: %ProgramFiles%\Microsoft SQL Server\
; To use the default path, do not specify the following parameter.

INSTALLSQLDIR=

;--------------------------------------------------------------------
; INSTALLSQLSHAREDDIR specifies a custom location for Integration Services
; Notification Services, Client Components, SQL Server Books Online and Samples.
; To use the default path, do not specify the following parameter. Default path is %ProgramFiles%\Microsoft SQL Server\

INSTALLSQLSHAREDDIR=

;--------------------------------------------------------------------
; INSTALLSQLDATADIR specifies the location for the SQL Server data files.
; Default: INSTALLSQLDIR\Data\
; To use the default path, do not specify the following parameter.

INSTALLSQLDATADIR=

;--------------------------------------------------------------------
; ADDLOCAL specifies which components to install. If ADDLOCAL is not
; specified, setup will fail.
; To install all components specify 'ADDLOCAL=ALL' on the command line.

ADDLOCAL=SQL_Engine,SQL_Data_Files,Client_Components,Connectivity

;--------------------------------------------------------------------
; INSTANCENAME is REQUIRED; for a default instance use MSSQLSERVER
; For shared components (IS, NS and client components) INSTANCENAME is not required.

;INSTANCENAME=MSSQLSERVER

INSTANCENAME=BlackBerry

;--------------------------------------------------------------------
; The services for SQL Server and Analysis Server are set auto start. To use the
;*ACCOUNT settings make sure to specify the DOMAIN, e.g. SQLACCOUNT=DOMAINNAME\ACCOUNT
; NOTE: When installing SQL_Engine 3 accounts are REQUIRED: SQLACCOUNT, AGTACCOUNT and
;SQLBROWSERACCOUNT.

;SQLACCOUNT="NT AUTHORITY\LOCAL SERVICE"

SQLACCOUNT="NT AUTHORITY\SYSTEM"

;--------------------------------------------------------------------
; To use the *AUTOSTART features, specify 1 to start automatically or 0 to start manually.
; NOTE: If you decide to start SQL Agent automatically, then SQL is also started automatically.
; If *AUTOSTART is not specified on the command line, startup is set to manual.

SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
AGTAUTOSTART=0

;--------------------------------------------------------------------
; To use Mixed mode authentication, use SECURITYMODE=SQL.
; If SECURITYMODE=SQL is not specified, then Windows Authentication only will be used by default.
; If you use SQL Authentication, you are REQUIRED to provide a strong system administrator (SA) password.
; If you use Windows Authentication, the SA account will be disabled.
; To set SA password specify SAPWD.

;SECURITYMODE=SQL
;SAPWD=password

SECURITYMODE=


;--------------------------------------------------------------------
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only),
;TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only),
;TCP= On
; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

DISABLENETWORKPROTOCOLS=0

;--------------------------------------------------------------------
; The ENABLERANU switch is used to configure Run as Normal User (User Instances).
; Set ENABLERANU = 0 to turn User Instances off.
; Set ENABLERANU = 1 (default) to turn User Instances on.
; Note: User Instances only apply to SQL Server Express SKUs.

ENABLERANU=0

;--------------------------------------------------------------------
; The ADDUSERASADMIN switch is used to add the setup user to the
; SQL Server 2005 System Administrator role. Members of the
; System Administrator role can perform any activity in the server.
; Set ADDUSERASADMIN=1 to add the setup user to the SQL Server System Administrator role

ADDUSERASADMIN=0

 

[JayKusch]

Before we "try" to change the default SQL installation paths and folder name(s) (which I am not sure we can do) ... what are you trying to accomplish by changing the folder names?

Thanks

J. Kusch

 

[Nicolus]

what are you trying to accomplish by changing the folder names?"

Jay, it's for clarification purposes. I don't like to hold my customers hostage, therefore I provide them with detailed installation and removal instructions on all aspects of their network and server. I have already written (with screenshots) manuals on how to install or reinstall BES under SQL 2000 nomenclature (MSSQL$INSTANCENAME). Now SQL 2005 uses different nomenclature of MSSQL.1, MSSQL.2, etc. This means that now I have to rewrite each customer's manuals based on what folder SQL is installed for BES.

I know my reasoning sounds trivial but when you are the contractor for 19 customers, you want things to be as harmonious across all installations.

 

[Nicolus]

Can something be added under the INSTALLSQLDIR= to wind up with a path that looks like C:\Program Files\Microsoft SQL\MSSQL$BlackBerry ?

 

[JayKusch]

I understand your concern as I have been a contractor and business owner that provided SQL Server services and applications.

Have to say that going to the level of changing directory structures for installation of applications seems a bit much, each to his own I guess - lol.

I am going to have to deffer to one of the other tech folk on this forum.

I am aware that in using the installsqldir variable, you are able to place the binaries in a user defined folder other than the default of "C:\Program Files\SQL Server" BUT I am not sure about the instance name ... it "should" work.

Take a look at this link searching on the word installsqldir.

If in using the variable to redirect the binary installed does not work, I would be REALLY hesitant at trying to kludge in a naming scheme that may cause a failed installation or worst yet, an installation that has issues later that are hard to track.

Just my 2 cents.

Good Luck!

Thanks

J. Kusch

 

[mrdenny]

All you can effect is the "C:\Program Files\Microsoft SQL Server\" portion of the path. You can't specify anything after that.

You'll need to adjust your documentation to match the new path of SQL Server 2005. Once SQL Server 2008 is used with BES the patch will change again.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog

 

[Nicolus]

Jay, and Denny,

Thank you for your assistance. It's kind of idiotic that such a limitation would exist.

I believe I've come up with a solution that i'd like to test out. I will be creating a SQL2000 instance, then upgrade it to 2005.

Denny, can you kindly give me a quick sql 2000 template that is in line with what I'm achieving with the template above?

Thank you again,

Nic

 

[JayKusch]

I beleive the upgrade process is going to create the same directory structure as would a clean install of 2005.


Thanks

J. Kusch

 

[mrdenny]

I'm not sure what an upgrade would do.

I'm not sure what changes would need to be made to the template file. It's been years since I've used a template file.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog

 

[Nicolus]

Gentlemen,

Again thank you for your participation. It worked. After installing SQL 2000, I went over it with SQL 2005 and chose the advanced installation option which allows you to choose the instance you want to upgrade. The upgrade upgrades the current folder.

FYI, SQL 2008 gods seemed to finally get it and give an option. So I downloaded SQL 2008 Express... Guess what, it is NOT compatible with BB! Oh the irony! LOL

 

[mrdenny]

I'm sure eventually BES will be compatible with SQL Server 2008.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog