Hi Tim,

I'm a DBIsam 3 CS customer and I'm very satisfyed with it.
There's is 2 important things that I was expecting for ElevateDB V2 in
order to buy it
- Replications
- Compact framework compatibility

these 2 items make EDB a real alternative to MS SQL server, with these 2
things Pocket PCs could make syncronizations with a EDB server.

and it seems that CF is not supported so I'm a little bit disapointed,
and I have to say that the support of Elevatesoft is so great that I
hope that one day I would be able to migrate to EDB when the CF will be
implemented..

regards

Armindo

Armindo,

<< and it seems that CF is not supported so I'm a little bit disapointed,
and I have to say that the support of Elevatesoft is so great that I hope
that one day I would be able to migrate to EDB when the CF will be
implemented.. >>

I'll see if I can add CF support to the EDB 2.0 upgrade.  It really is
nothing more than adding it to the builds since the EDB .NET data provider
is basically ready-to-go in this respect.

As for replication, I think you'll find the EDB 2.0 replication to be very
cool.   As it stands right now, it does bi-directional replication with some
very easy-to-use SQL statements for setting up publishers, subscribers, and
subscriptions, as well as performing the synchronizations with publishers.
The synchronizations are always subscriber-driven (pull-only, but allowing
for changes to be replicated back to the publisher also), but that's a minor
point for most installations.  At some point I'll be extending the
architecture to allow for pushing changes down to other ElevateDB Servers,
but that will most likely be customized so that it is specific to a
fail-safe server arrangement instead.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,
> I'll see if I can add CF support to the EDB 2.0 upgrade.  It really is
> nothing more than adding it to the builds since the EDB .NET data provider
> is basically ready-to-go in this respect.

Waiting for it  
Today we use SQL server compact on the PDA side and we have done our own
 replication system with firebird on the server.
ButSQL server compact consume a lot of memory and is not embeded, so
it's quite slow.
With the CF engine version be embeded ?


> As for replication, I think you'll find the EDB 2.0 replication to be very
> cool.   As it stands right now, it does bi-directional replication with some
> very easy-to-use SQL statements for setting up publishers, subscribers, and
> subscriptions, as well as performing the synchronizations with publishers.
> The synchronizations are always subscriber-driven (pull-only, but allowing
> for changes to be replicated back to the publisher also), but that's a minor
> point for most installations.  At some point I'll be extending the
> architecture to allow for pushing changes down to other ElevateDB Servers,
> but that will most likely be customized so that it is specific to a
> fail-safe server arrangement instead.
>

Does it support merge replication like SQL server ?

Thanks

Armindo

Armindo,

<< Today we use SQL server compact on the PDA side and we have done our own
replication system with firebird on the server.  ButSQL server compact
consume a lot of memory and is not embeded, so it's quite slow.
With the CF engine version be embeded ? >>

The .NET data provider is a single assembly (.dll).   I'm not exactly sure
how it would work if you linked in this assembly into your application in
terms of the factory classes, but it should work if you were to directly
call the proper classes for ElevateDB (EDBConnection, EDBCommand, etc.).

<< Does it support merge replication like SQL server ? >>

That's the only type of replication that it does.

--
Tim Young
Elevate Software
www.elevatesoft.com