VistaDB Database

[Johnny Jörgensen]

Hi all

I just saw an ad in the latest ComponentSource newsletter for a database
engine called VistaDB 3.0.

http://www.vistadb.net/default.asp

It looks very interesting as a database engine for smaller applications
where you would normally use access. Plus it can be embedded into the exe.

I've just started doing a small database application, and my concern has
been this: Should I use access or SQL server?

Access is simpler and actually quite sufficient for my needs (very small
database - only a few tables), but it seems old fahioned to me. But at the
same time, I've been reluctant to choose SQL Server because it complicates
the administration and deployment. Access is simply a file you copy, but
with SQL server you have to install the engine and check in the installation
if it exists, attach the database... Not extremely complicated but still a
little overkill for my application.

So I though of testing VistaDB, but I just wonder if anybody knows of it and
has experiences using it they would like to share???

Cheers,
Johnny J.

[Spam Catcher]

"Johnny Jörgensen" <jo**@altcom.se wrote in
news:#h******** ******@TK2MSFTN GP04.phx.gbl:

It looks very interesting as a database engine for smaller
applications where you would normally use access. Plus it can be
embedded into the exe.

Firebird Database is also embeddable and very tiny - 250KB? It's free too.

Access is simpler and actually quite sufficient for my needs (very
small database - only a few tables), but it seems old fahioned to me.

Access is fine for small applications. You can always upsize to SQL Server
if Access is insufficient.

[Lloyd Sheen]

"Johnny Jörgensen" <jo**@altcom.se wrote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..

Hi all

I just saw an ad in the latest ComponentSource newsletter for a database
engine called VistaDB 3.0.

http://www.vistadb.net/default.asp

It looks very interesting as a database engine for smaller applications
where you would normally use access. Plus it can be embedded into the exe.

I've just started doing a small database application, and my concern has
been this: Should I use access or SQL server?

Access is simpler and actually quite sufficient for my needs (very small
database - only a few tables), but it seems old fahioned to me. But at the
same time, I've been reluctant to choose SQL Server because it complicates
the administration and deployment. Access is simply a file you copy, but
with SQL server you have to install the engine and check in the
installation if it exists, attach the database... Not extremely
complicated but still a little overkill for my application.

So I though of testing VistaDB, but I just wonder if anybody knows of it
and has experiences using it they would like to share???

Cheers,
Johnny J.

Take a look at SQL Express. It is SQL Server without some of the enterprise
pieces. Just install create your database and tables and away you go.
Almost no admin.

LS

[simon]

On Jun 8, 5:06 pm, "Johnny Jörgensen" <[e-mail] wrote:

Hi all

I just saw an ad in the latest ComponentSource newsletter for a database
engine called VistaDB 3.0.

http://www.vistadb.net/default.asp

So I though of testing VistaDB, but I just wonder if anybody knows of it and
has experiences using it they would like to share???

I'm a VistaDB user of about 3 years standing and have two products
based on VistaDB that are distributed quite widely.

I chose VistaDB over Access so that the data that goes out with my
product would be secure (Blowfish encryption), over SQL Express due to
my concern about it's size and possible installion problems and over
SQL Everywhere (or whatever) as that product is single-user by design.
There's also a great support forum and I suggest you have a browse
there to see what others have to say.

Simon

[VistaDB]

Access is simpler and actually quite sufficient for my needs (very small

database - only a few tables), but it seems old fahioned to me. But at the
same time, I've been reluctant to choose SQL Server because it complicates
the administration and deployment. Access is simply a file you copy, but
with SQL server you have to install the engine and check in the installation
if it exists, attach the database... Not extremely complicated but still a
little overkill for my application.

Here are the biggest values for VistaDB:

100% managed code
No CPU / RAM Limits (SQL CE has a lot of limits)
You can XCopy deploy the database engine with your app.
We work with isolated storage, in memory databases, and on disk (local
and across a LAN). We have plans for a server later this year.

We run under Compact Framework, 1.1, 2.0 and Mono today. This means
you can Xcopy and deploy to a lot of environments.

We are also at work on a LINQ provider for later this year as well.

We have all the same datatypes from TSQL as SQL Server, and we try to
use the same syntax. That means upsizing to SQL Server is a lot less
work than Access (which has totally different types and syntax).

So we are a good fit for desktop databases where Access is too little,
and SQL Server is too much.

So I though of testing VistaDB, but I just wonder if anybody knows of it and
has experiences using it they would like to share???

Well, since I am the president of the company my impressions may be a
bit skewed. :)

Feel free to visit our forums to ask questions:

http://www.vistadb.net/forums

[Johnny Jörgensen]

OK, but what is missing from the VistaDB website is a speed and performance
comparison between the other databases, and I'm interested in knowing that
before making a choice...

Cheers,
Johnny J.
"VistaDB" <vi*****@gmail. comwrote in message
news:11******** **************@ m36g2000hse.goo glegroups.com.. .

>Access is simpler and actually quite sufficient for my needs (very small
database - only a few tables), but it seems old fahioned to me. But at
the
same time, I've been reluctant to choose SQL Server because it
complicates
the administration and deployment. Access is simply a file you copy, but
with SQL server you have to install the engine and check in the
installation
if it exists, attach the database... Not extremely complicated but still
a
little overkill for my application.

Here are the biggest values for VistaDB:

100% managed code
No CPU / RAM Limits (SQL CE has a lot of limits)
You can XCopy deploy the database engine with your app.
We work with isolated storage, in memory databases, and on disk (local
and across a LAN). We have plans for a server later this year.

We run under Compact Framework, 1.1, 2.0 and Mono today. This means
you can Xcopy and deploy to a lot of environments.

We are also at work on a LINQ provider for later this year as well.

We have all the same datatypes from TSQL as SQL Server, and we try to
use the same syntax. That means upsizing to SQL Server is a lot less
work than Access (which has totally different types and syntax).

So we are a good fit for desktop databases where Access is too little,
and SQL Server is too much.

>So I though of testing VistaDB, but I just wonder if anybody knows of it
and
has experiences using it they would like to share???

Well, since I am the president of the company my impressions may be a
bit skewed. :)

Feel free to visit our forums to ask questions:

http://www.vistadb.net/forums