http://msdn.microsoft.com/library/de...seoverview.asp
[... big long snip ...]
SQL Server Express was developed with two distinct uses in mind. The first
is as a server product, especially as a Web server or a database server.
The second is as a local client data store where the application data
access does not depend on the network. Ease of use and simplicity are key
design goals.
The three main usage scenarios for SQL Server Express are:
Non-professional developers building Web applications
ISVs redistributing SQL Server Express as a low-end server or client data
store
Hobbyists building basic client/server applications
[... more snipping ...]
Visual Studio Integration
SQL Server Express is installed with all the 32-bit editions of Visual
Studio. Visual Studio installs SQL Server Express using the instance name
SQLEXPRESS. In SQL Server Express Technical Preview, the applications rely
on the SQLEXPRESS instance name, but this could change in future. The goal
of Visual Studio and SQL Server Express integration is to make database
access with SQL Server Express as simple and easy as working with Jet.
[... more snipping ...]
Comparison with Jet
SQL Server Express is based on the latest SQL Server 2005 technology,
while Jet has been in service pack and maintenance stage for quite some
time. All the latest and greatest features, such as CLR integration and
XML support, are available only in SQL Server Express. The reliability and
scalability story of SQL Server Express is also great. Applications
written to SQL Server Express can easily move to SQL Server Standard or
Enterprise editions, while Jet is more difficult to scale up. SQL Server
Express also provides finer-grained security control over its database
files. With the Visual Studio 2005 integration and the Application XCopy
feature, we are bringing the ease of use of Jet to SQL ServeR.
Darryl Kerkeslager
