Embedded on Server

[John Reynolds]

I have installed the XP Embedded tools on an XP workstation. I have
installed the XP Embedded databases on a 2003 Server. The installation put
the repositories on drive D. I cannot apply SP2 to the databases. It tells
me there are no databases installed. If I try to re-install the databases,
it says they are installed and I am asked to modify/repair/remove.

What am I doing wrong? Is this due to the repositories being on drive D?
If so, how would I move them to drive C? Uninstalling and reinstalling
still puts them on drive D.

Thank you for any help!
J-

 

[David Harris]

I have installed the XP Embedded tools on an XP workstation. I have installed
the XP Embedded databases on a 2003 Server. The installation put the
repositories on drive D. I cannot apply SP2 to the databases. It tells me
there are no databases installed. If I try to re-install the databases, it
says they are installed and I am asked to modify/repair/remove.

What am I doing wrong? Is this due to the repositories being on drive D? If
so, how would I move them to drive C? Uninstalling and reinstalling still
puts them on drive D.

Thank you for any help!
J-

If you are using the database server that comes with Embedded Studio, it is only
designed to run on the local machine and service a single user on the same
machine. If you try to install the server and/or database on a remote path, the
server gets confused so it will not work correctly.
If you want to have the database running on any other machine and access it
remotely you will need to install the full version of SQL Server on that
platform and install the database using that server.

When you install the database it tries to put it onto the drive that has the
most space on it. To get around this choose the 'custom' option during install.
That will allow you to specify where you want it installed.

David

 

[John Reynolds]

OK. Here is what I have done:

- Uninstalled XP Embedded databases from Windows 2003 Server
- Installed SQL Server on Windows 2003 Server
- Installed XP Embedded databases on Windows 2003 Server
-- Did not perform a custom install so the installation was performed
to Drive D: du to it being the largest
- Attempted install of SP2. Receive message that databases are not
installed.

Any idea why I'm getting this error?

Thanks!
J-

 

[Guest]

Hi,

I want to store the database and repositories on our network so that
everthing will be neatly backuped every day. I just want to access the
database with 1 workstation that will have the toolkit and a the SQL server
installed. So it's not a group devellopment thing but safety.

Please confirm or correct my interpretation:

- When using the SQLSERVER that comes with the XPE toolkit the component
database can ONLY reside locally on the system that is running the SQL
service. It is NOT possible for a user to change the path to the database.

- When the database is located on a networkshare the "full version of SQL
Server" must be installed in order to use this database. It IS possible for a
user to change the path to the database.

Additional questions:

- MS offers the free "SQL Server 2005 Express Edition". Does this server
meet my requirements?
- How does the standard toolkit SQL server find the database. It's not on
the repositories share and it's on 'just' a local disk, so how does it know?

Thijs

 

[Sean Liming \(eMVP\)]

The tools can be made to chage to different databases through the Component
Database Manager tool weather the database is SQL or MSDE.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.

 

[Guest]

I know I can set the tools to different database servers through the "MS
Component Database Manager" tab "Database", section "Database connection".
But is it possible to cahnge the fysical location of the component database
and still use MSDE. I can't seem to find how the MSDE knows where to find the
component database. Dave Harris wrote
=====
If you try to install the server and/or database on a remote path, the
server gets confused so it will not work correctly.
=====

So I assume that using the component databaes from a remote path doesn't work.

The question is if the "SQL Server 2005 Express Edition" IS able to work
with a component database on a remote path.

Thijs