What is the best way to distribute an app that uses Sql Server Express?

  • Thread starter Thread starter Greg
  • Start date Start date
G

Greg

From my dark past I seem to remember that when distributing an app that
talked to an access database, the end user did not need to have access
installed on their machine in order for an application to talk to an
access database file - the Jet engine looked after everything.

What is the score with SQL Server Express? Will users need this
installed on their machines? I guess it is possible to write a script
that installs this along with my app but I am wondering if they really
need SQL server express on their machine.

Greg.
 
The difference is this:

For Access, the Jet drivers operate directly on the database files (.mdb).
This is why you don't need Access on the computer to use MS Access
databases.

For SQL Server and its variations (MSDE, Express, etc), the drivers
communicate via the SQL engine. They do not operate directly against the
database files. Because of this, you actually need some version of SQL
server on the machine to use the database.

So yes, you do need to install SQL Server Express with the app.

Pete
 
Hi Greg,
I am not clear on whether this is a standalone database or a 'common'
database shared by many users of your app.
If it is a common database than you only need SQL Server installed on the
one machine where the database resides. The .Net clients on each of the
other machines will communicate with it.
regards
Bob
 
Thanks Pete & Bob.

It is a standalone database. 5 tables max, though each one will be
quite big (several thousand tuples). Is there an easy way to
incorporate the database installation within the installation of my app
i.e. a one click installation for everything?

Would a different database make things easier for me? Would I be better
off using Access?

Thanks again.

Greg.
 
Back
Top