Defining solution architecture

[Guest]

Hi all

I’m developing a solution which is going to run in an embedded device (Windows CE.NET & SH3 processor)

This device is a self-contained black box with no screen.

The main application in this device will be a Windows Service - with various threads - accessing a local database.

Any interaction with the embedded device (for tasks such as configuration) will be performed through web pages. Those web pages (ASP) have to have access to the database as well.

More than one application may use the database at once. For example, the Windows Service might be recording a entry at the same time a user is configuring something. Or even two different threads in the Windows Service accessing two different tables through 2 different connections

We are now deciding which database solution to use in this embedded device
In order to reduce our development time, we would like to reuse some of our existing applications (most of them access database through an ADO connection)

So, the requirements for this database basically are

- Windows CE.NET compatibl
- Multi-connection capabilities
- SQL compliant (including UPDATES!
- Acceptable performance (should not interfere with ordinary processing
- ADO compatible (optional
- Low memory footprint (optional

SQL Server CE seems to be the closest I can get, but it doesn’t seem to support multi-connection.

The CEDB doesn’t accept multi-connection nor UPDATE queries

I heard that Laguna will have multi-connection capabilities, but I can’t wait indefinitely for it, as we have a deadline. However, any info on Laguna is useful

Can you guys tell me which database should I use

If I forgot to mention something, my e-mail is (e-mail address removed)

TI

August

 

[Chris Tacke, eMVP]

the next version of SQL Server CE is the only thing I'm aware of that meets
your critereia, and it's release is ties to Yukon, so you're probably a year
or more away from the release on it. Now you could always use the current
version with a data access layer that maintains the only DB connection and
have all of your other apps talk to that class instead of the DB directly.

-Chris

Hi all,

I'm developing a solution which is going to run in an embedded device

(Windows CE.NET & SH3 processor).

This device is a self-contained black box with no screen.

The main application in this device will be a Windows Service - with

various threads - accessing a local database.

Any interaction with the embedded device (for tasks such as configuration)

will be performed through web pages. Those web pages (ASP) have to have
access to the database as well.

More than one application may use the database at once. For example, the

Windows Service might be recording a entry at the same time a user is
configuring something. Or even two different threads in the Windows Service
accessing two different tables through 2 different connections.

We are now deciding which database solution to use in this embedded device.
In order to reduce our development time, we would like to reuse some of

our existing applications (most of them access database through an ADO
connection).

So, the requirements for this database basically are:

- Windows CE.NET compatible
- Multi-connection capabilities.
- SQL compliant (including UPDATES!)
- Acceptable performance (should not interfere with ordinary processing)
- ADO compatible (optional)
- Low memory footprint (optional)

SQL Server CE seems to be the closest I can get, but it doesn't seem to support multi-connection.

The CEDB doesn't accept multi-connection nor UPDATE queries.

I heard that Laguna will have multi-connection capabilities, but I can't

wait indefinitely for it, as we have a deadline. However, any info on Laguna
is useful.

 

[Augusto]

Sound like a good idea.

Thank you, Chris.

the next version of SQL Server CE is the only thing I'm aware of that meets
your critereia, and it's release is ties to Yukon, so you're probably a year
or more away from the release on it. Now you could always use the current
version with a data access layer that maintains the only DB connection and
have all of your other apps talk to that class instead of the DB directly.

-Chris




(Windows CE.NET & SH3 processor).
various threads - accessing a local database. configuration)
will be performed through web pages. Those web pages (ASP) have to have
access to the database as well.
Windows Service might be recording a entry at the same time a user is
configuring something. Or even two different threads in the Windows Service
accessing two different tables through 2 different connections.
our existing applications (most of them access database through an ADO
connection).
wait indefinitely for it, as we have a deadline. However, any info on Laguna
is useful.