Supporting SP1 and SP2 Databases

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Microsoft states you should use 2 separate machines, one for maintaining SP1
builds and another for SP2 builds. This sounds like this could be a
maintenance nightmare. Is there any way to use the same server but just use
different databases? For example, an SP1 database and an SP2 database on the
same computer. Also mentioned is to restore an SP1 database and repository
for supporting my SP1 images. This also sounds like a nightmare. Anyone else
doing this?
 
Brad,

How do i get the attached batch file?

Brad Combs said:
Tim,

It's not supported officially but take a look at the attached batch file. I
edited out our customer databases but I'm using this to manage 10 different
databases on 1 build server. Just change C:\XPe to whatever your directory
with the DB's is. (C:\Windows Embedded Data for example).

HTH,
Brad
 
Tim,

There is currently no way to support XPe SP1 and SP2 database running the same time on the same server [dev] machine.
This is what I outlined in my reply to your previous post.

But you can go by one of the following routes:
- Have two server machines running each database separately. Then on dev machines it is easy to switch between databases and
repositories.
- Detach database of fly (use osql utility or SQL Enterprise Manager or just stop MSDE service with sc.exe or "net stop
MSSQLSERVER" command)
replace the Mantis LDF file under the \Windows Embedded Data folder on the server and attach to the database again.
- Have only SP2 server machine running. You can still build and support SP1 images. (a little bit risky when it comes to SP1
QFEs)
 
KM, thanks for the help.

KM said:
Tim,

There is currently no way to support XPe SP1 and SP2 database running the same time on the same server [dev] machine.
This is what I outlined in my reply to your previous post.

But you can go by one of the following routes:
- Have two server machines running each database separately. Then on dev machines it is easy to switch between databases and
repositories.
- Detach database of fly (use osql utility or SQL Enterprise Manager or just stop MSDE service with sc.exe or "net stop
MSSQLSERVER" command)
replace the Mantis LDF file under the \Windows Embedded Data folder on the server and attach to the database again.
- Have only SP2 server machine running. You can still build and support SP1 images. (a little bit risky when it comes to SP1
QFEs)

--
Regards,
KM

Microsoft states you should use 2 separate machines, one for maintaining SP1
builds and another for SP2 builds. This sounds like this could be a
maintenance nightmare. Is there any way to use the same server but just use
different databases? For example, an SP1 database and an SP2 database on the
same computer. Also mentioned is to restore an SP1 database and repository
for supporting my SP1 images. This also sounds like a nightmare. Anyone else
doing this?
 
KM,

What if I install the sp1 compoent database, stop service and rename
database, install component database again with sp2. if i need to access the
sp1 database, stop service, rename sp2 database and then rename sp1 database
to mantis?

KM said:
Tim,

There is currently no way to support XPe SP1 and SP2 database running the same time on the same server [dev] machine.
This is what I outlined in my reply to your previous post.

But you can go by one of the following routes:
- Have two server machines running each database separately. Then on dev machines it is easy to switch between databases and
repositories.
- Detach database of fly (use osql utility or SQL Enterprise Manager or just stop MSDE service with sc.exe or "net stop
MSSQLSERVER" command)
replace the Mantis LDF file under the \Windows Embedded Data folder on the server and attach to the database again.
- Have only SP2 server machine running. You can still build and support SP1 images. (a little bit risky when it comes to SP1
QFEs)

--
Regards,
KM

Microsoft states you should use 2 separate machines, one for maintaining SP1
builds and another for SP2 builds. This sounds like this could be a
maintenance nightmare. Is there any way to use the same server but just use
different databases? For example, an SP1 database and an SP2 database on the
same computer. Also mentioned is to restore an SP1 database and repository
for supporting my SP1 images. This also sounds like a nightmare. Anyone else
doing this?
 
Tim,

That should work.
Btw, replace both MantisSQLDB_Data.mdf (the database) and MantisSQLDB_Log.ldf (transaction log) files.

But keep in mind that you are using the same Repository locations for both SPs in your scenario. Not a big deal since the SP2 update
repository is separate from SP1. But again, may be a little bit risky when it comes to installing various QFEs (needs to be tested
well, I guess).
Or you can also have two separate physical Repositories on the drive. All you have to do during switch then is to change the network
share target (default repository share name is Repositories).

--
Regards,
KM

KM,

What if I install the sp1 compoent database, stop service and rename
database, install component database again with sp2. if i need to access the
sp1 database, stop service, rename sp2 database and then rename sp1 database
to mantis?

KM said:
Tim,

There is currently no way to support XPe SP1 and SP2 database running the same time on the same server [dev] machine.
This is what I outlined in my reply to your previous post.

But you can go by one of the following routes:
- Have two server machines running each database separately. Then on dev machines it is easy to switch between databases and
repositories.
- Detach database of fly (use osql utility or SQL Enterprise Manager or just stop MSDE service with sc.exe or "net stop
MSSQLSERVER" command)
replace the Mantis LDF file under the \Windows Embedded Data folder on the server and attach to the database again.
- Have only SP2 server machine running. You can still build and support SP1 images. (a little bit risky when it comes to SP1
QFEs)

--
Regards,
KM

Microsoft states you should use 2 separate machines, one for maintaining SP1
builds and another for SP2 builds. This sounds like this could be a
maintenance nightmare. Is there any way to use the same server but just use
different databases? For example, an SP1 database and an SP2 database on the
same computer. Also mentioned is to restore an SP1 database and repository
for supporting my SP1 images. This also sounds like a nightmare. Anyone else
doing this?
 
Back
Top