Can XPe SP1 and SP2 co-exist on the same development machine?

Hi Mark,

1. Stop DB.
2. Duplicate SP1 folder named "Windows Embedded Data" to let say WEDBKP folder name.
3. Install SP2.

Make a batch file that will do following.
1. Stop DB.
2. Close net share on Repositories.
3. Rename "Windows Embedded Data" to let say WEDBKP2
4. Rename WEDBKP to "Windows Embedded Data"
6. Rename WEDBKP2 to WEDBKP
7. Start net share on Repositories.
8. Start DB.

Regards,
Slobodan

"Mark K Vallevand" <mark.vallevand@unisys.com> wrote in message news:%23gjNqJH3EHA.524@TK2MSFTNGP09.phx.gbl...

> The boss says XPe SP1 for product A, and XPe SP2 for product B.
>
> I have one workstation. Can I have both SP1 and SP2 on it?
>
> When SP2 is installed, are the SP1 components overwritten or removed from
> the database? (I don't think so.) Maybe I can be selective about upgrading
> components in the product A SLX file and keep it at SP1.
>
> Advice is greatly appreciated.
>
> --
> Regards.
> Mark K Vallevand
>
>

On Tue, 7 Dec 2004 18:46:47 +0100, "Slobodan Brcin \(eMVP\)"
<sbrcin@ptt.yu> wrote:

> Hi Mark,
>
> 1. Stop DB.
> 2. Duplicate SP1 folder named "Windows Embedded Data" to let say WEDBKP folder name.
> 3. Install SP2.
>
> Make a batch file that will do following.
> 1. Stop DB.
> 2. Close net share on Repositories.
> 3. Rename "Windows Embedded Data" to let say WEDBKP2
> 4. Rename WEDBKP to "Windows Embedded Data"
> 6. Rename WEDBKP2 to WEDBKP
> 7. Start net share on Repositories.
> 8. Start DB.

Hi, Slobodan

There is some information about the database in the system databases too,
so maybe instead of stopping the server and swapping the .mdf and .ldf
files underneath it, it could be safer to detach one version and attach the
other.

This can be done from a batch file too, through oqsl.exe (in the SQL Server
installation path, .\80\Tools\binn subdirectory).

osql -E -Q "sp_detach_db 'MantisSQLDB'"

> 2. Close net share on Repositories.
> 3. Rename "Windows Embedded Data" to let say WEDBKP2
> 4. Rename WEDBKP to "Windows Embedded Data"
> 6. Rename WEDBKP2 to WEDBKP
> 7. Start net share on Repositories.

set f1=X:\Windows Embedded Data\MantisSQLDB_Data.mdf
set f2=X:\Windows Embedded Data\MantisSQLDB_Log.ldf
osql -E -Q "sp_attach_db 'MantisSQLDB', '%f1%', '%f2%'"

I used environment variables for the filenames only to shorten the last
command line, so it's not broken in this post by the time you read it.



There's one drawback: sp_detach_db will fail if the database is still open
somewhere, and checking the return value in a single line sounds easier
than it is.

I thought executing the command as

osql -E -Q "exit(exec sp_detach_db 'MantisSQLDB')"

should store the result in %errorlevel%, but it looks like that doesn't
work with stored procedures (I always get errorlevel = -100).

Maybe we could ask for help in one of the SQL server groups

Hi Lucvdv,

You are right that this look like better approach. But my DB knowledge is very limited and I'm not too eager to improve it soon.
(too high level for my taste).

Regards,
Slobodan


"Lucvdv" <replace_name@null.net> wrote in message news:vuddr0198qn0lirn5dgt2cbv484sqeom3c@4ax.com...

> On Tue, 7 Dec 2004 18:46:47 +0100, "Slobodan Brcin \(eMVP\)"
> <sbrcin@ptt.yu> wrote:
>

> > Hi Mark,
> >
> > 1. Stop DB.
> > 2. Duplicate SP1 folder named "Windows Embedded Data" to let say WEDBKP folder name.
> > 3. Install SP2.
> >
> > Make a batch file that will do following.
> > 1. Stop DB.
> > 2. Close net share on Repositories.
> > 3. Rename "Windows Embedded Data" to let say WEDBKP2
> > 4. Rename WEDBKP to "Windows Embedded Data"
> > 6. Rename WEDBKP2 to WEDBKP
> > 7. Start net share on Repositories.
> > 8. Start DB.

>
>
> Hi, Slobodan
>
> There is some information about the database in the system databases too,
> so maybe instead of stopping the server and swapping the .mdf and .ldf
> files underneath it, it could be safer to detach one version and attach the
> other.
>
> This can be done from a batch file too, through oqsl.exe (in the SQL Server
> installation path, .\80\Tools\binn subdirectory).
>
> osql -E -Q "sp_detach_db 'MantisSQLDB'"

> > 2. Close net share on Repositories.
> > 3. Rename "Windows Embedded Data" to let say WEDBKP2
> > 4. Rename WEDBKP to "Windows Embedded Data"
> > 6. Rename WEDBKP2 to WEDBKP
> > 7. Start net share on Repositories.

> set f1=X:\Windows Embedded Data\MantisSQLDB_Data.mdf
> set f2=X:\Windows Embedded Data\MantisSQLDB_Log.ldf
> osql -E -Q "sp_attach_db 'MantisSQLDB', '%f1%', '%f2%'"
>
> I used environment variables for the filenames only to shorten the last
> command line, so it's not broken in this post by the time you read it.
>
>
>
> There's one drawback: sp_detach_db will fail if the database is still open
> somewhere, and checking the return value in a single line sounds easier
> than it is.
>
> I thought executing the command as
>
> osql -E -Q "exit(exec sp_detach_db 'MantisSQLDB')"
>
> should store the result in %errorlevel%, but it looks like that doesn't
> work with stored procedures (I always get errorlevel = -100).
>
> Maybe we could ask for help in one of the SQL server groups
>

I just noticed this in the SP2 Rel.Notes: "Dual installations of the database are not supported, whether on the same or different
drives or partitions."

KM

> The boss says XPe SP1 for product A, and XPe SP2 for product B.
>
> I have one workstation. Can I have both SP1 and SP2 on it?
>
> When SP2 is installed, are the SP1 components overwritten or removed from
> the database? (I don't think so.) Maybe I can be selective about upgrading
> components in the product A SLX file and keep it at SP1.
>
> Advice is greatly appreciated.
>
> --
> Regards.
> Mark K Vallevand
>
>