eval sp2, sp_password?



sam parker
07-09-2005, 10:25 PM
I just downloaded the XPe/SP2 eval kit. The process is to install SP1 tools
and the DB and then upgrade to SP2. When I tried to upgade the DB Engine,
the installer complained that my SA password was set to blank. Of course, I
was never given a chance to create this password but I was told I must use
sp_password to make the password stronger or set BLANKSAPWD=1. I assume
these are references to SQL server admin functions that I am not aware of in
the XPe distribution. Creating the environment variable BLANKSAPWD=1 didn't
help (bad guess), and the readme for whatever was included in SQL had no
reference to this issue. Can someone tell me how to proceed since the
installer refuses to upgrade my DB engine?

Scott Figg
07-09-2005, 10:25 PM
One way is, to go to the SQLMSDE directory on the XPe Service Pack 2 CD and
run the setup with the switch to set the SAPWD.

Command would be

setup SAPWD="insert a SA-Password"

Not recommended but you can ignore the SA Password by using the switch
BLANKSAPWD=1

This is all documented in the sp3readme.htm file located in the SQLMSDE
directory.

"sam parker" <samparker@discussions.microsoft.com> wrote in message
news:7E0F4AEA-BFFC-43CC-B960-3ACD55A13BD4@microsoft.com...
> I just downloaded the XPe/SP2 eval kit. The process is to install SP1
tools
> and the DB and then upgrade to SP2. When I tried to upgade the DB Engine,
> the installer complained that my SA password was set to blank. Of course,
I
> was never given a chance to create this password but I was told I must use
> sp_password to make the password stronger or set BLANKSAPWD=1. I assume
> these are references to SQL server admin functions that I am not aware of
in
> the XPe distribution. Creating the environment variable BLANKSAPWD=1
didn't
> help (bad guess), and the readme for whatever was included in SQL had no
> reference to this issue. Can someone tell me how to proceed since the
> installer refuses to upgrade my DB engine?

Scott Figg
07-09-2005, 10:25 PM
Sorry, I didn't put the whole run command in, it woud be........

setup /upgradesp sqlrun sapwd="insert your password"


-Scott Figg



"Scott Figg" <sfigg@arrow.com.NOSPAM> wrote in message
news:#V6$#vsYFHA.1148@tk2msftngp13.phx.gbl...
> One way is, to go to the SQLMSDE directory on the XPe Service Pack 2 CD
and
> run the setup with the switch to set the SAPWD.
>
> Command would be
>
> setup SAPWD="insert a SA-Password"
>
> Not recommended but you can ignore the SA Password by using the switch
> BLANKSAPWD=1
>
> This is all documented in the sp3readme.htm file located in the SQLMSDE
> directory.
>
> "sam parker" <samparker@discussions.microsoft.com> wrote in message
> news:7E0F4AEA-BFFC-43CC-B960-3ACD55A13BD4@microsoft.com...
> > I just downloaded the XPe/SP2 eval kit. The process is to install SP1
> tools
> > and the DB and then upgrade to SP2. When I tried to upgade the DB
Engine,
> > the installer complained that my SA password was set to blank. Of
course,
> I
> > was never given a chance to create this password but I was told I must
use
> > sp_password to make the password stronger or set BLANKSAPWD=1. I assume
> > these are references to SQL server admin functions that I am not aware
of
> in
> > the XPe distribution. Creating the environment variable BLANKSAPWD=1
> didn't
> > help (bad guess), and the readme for whatever was included in SQL had no
> > reference to this issue. Can someone tell me how to proceed since the
> > installer refuses to upgrade my DB engine?
>
>

KM
07-09-2005, 10:25 PM
Sam,

>I just downloaded the XPe/SP2 eval kit. The process is to install SP1
>tools
> and the DB and then upgrade to SP2. When I tried to upgade the DB Engine,
> the installer complained that my SA password was set to blank. Of course,
> I
> was never given a chance to create this password but I was told I must use
> sp_password to make the password stronger or set BLANKSAPWD=1. I assume
> these are references to SQL server admin functions that I am not aware of
> in
> the XPe distribution. Creating the environment variable BLANKSAPWD=1
> didn't
> help (bad guess), and the readme for whatever was included in SQL had no
> reference to this issue. Can someone tell me how to proceed since the
> installer refuses to upgrade my DB engine?

You don't necessarily need to upgrade the DB engine (IIRC, it is either the
same version of MSDE or just latest SP for MSDE).
You can safily skip that step.

KM


eval sp2, sp_password?