"Lloyd Dupont" wrote:

> I want to toy with an embeded database for shareware application.
> I would like to know better SqlServer as well.
> However, correct me if I'm wrong, but it seems that as much as I would like
> to play with SqlServerExpress it seems higly unfit to this kind of
> application for the following reasons:
> - +20Mb to the install plus strange question to answer (for the clueless
> user)
> - Even though SqlServer express is installed your consumer application could
> fail if the service is, for some reason, off.
> - Even though SqlServer express is up and running you might not have connect
> access right to it, or right to create a new (file based) database (if need
> to), or maybe the server name is not what you expect and it can't be guess
> (or could 127.0.0.1 be used?)
>
> Because of these problem I was thinking to use Firebird (real, embeded, file
> based, database engine).
> Is the Procedural SQl language of Firebird the same as SqlServer express?
> Would it grows my SqlServer understanding to play with Firebird?
>
>
>

> but I see no problem with going
> with Firebird as a database engine for your application. It certainly does
> have a much smaller footprint. SQL Express contains a lot more for the
> price
> (;->), but you may not need the firepower for your application, so I can
> understand the size issue.
>
> As for the SQL question. With all database engines you have ANSI SQL and
> proprietary SQL as options. If you stick with ANSI standard syntax, you
> will
> be able to use what you learn with both. This will not help you with T-SQL
> specific commands, however. So, yes, Firebird will help you, but not as
> much
> as working in SQL Express.
>

"Lloyd Dupont" wrote:

> >I am not sure I agree with your concerns,
> Do I have false assumptions?
> Or do you just think that although what I said is true, it's not much an
> issue in many case?
>
> > but I see no problem with going
> > with Firebird as a database engine for your application. It certainly does
> > have a much smaller footprint. SQL Express contains a lot more for the
> > price
> > (;->), but you may not need the firepower for your application, so I can
> > understand the size issue.
> >
> > As for the SQL question. With all database engines you have ANSI SQL and
> > proprietary SQL as options. If you stick with ANSI standard syntax, you
> > will
> > be able to use what you learn with both. This will not help you with T-SQL
> > specific commands, however. So, yes, Firebird will help you, but not as
> > much
> > as working in SQL Express.
> >
> Allright, good to know!
> Thanks you!
>
>
>

"Steven Ramacher" <sramacher@community.nospam> wrote in message
news:76C53A4D-2A2C-428F-ADF0-BCA1F37FBAC9@microsoft.com...
>I believe that you can script the installation for a silent installation of
> SQL Express 2005, and X-Copy your database. SQL server is a more feature
> rich
> database engine, but there is a price to pay in foot print size. In my
> opinion you would be better off scripting the installation of SQL server
> in
> your installer package and x-copy your database.
> I have been using Interbase/Firebird for sometime now and have had great
> success. There are subtle differences in the way you construct your SQL
> statements, for example you have to use quotes around table names that are
> mixed cased or have spaces in them such as "First Name" instead of [First
> Name]. One consideration that you must make is that there is no out of the
> box way to protect your connection string with Firebird. Firebird is very
> fast and is a great fit for many users.
>
> Good Luck,
>
> --
> Steven
>
>
> "Lloyd Dupont" wrote:
>
>> >I am not sure I agree with your concerns,
>> Do I have false assumptions?
>> Or do you just think that although what I said is true, it's not much an
>> issue in many case?
>>
>> > but I see no problem with going
>> > with Firebird as a database engine for your application. It certainly
>> > does
>> > have a much smaller footprint. SQL Express contains a lot more for the
>> > price
>> > (;->), but you may not need the firepower for your application, so I
>> > can
>> > understand the size issue.
>> >
>> > As for the SQL question. With all database engines you have ANSI SQL
>> > and
>> > proprietary SQL as options. If you stick with ANSI standard syntax, you
>> > will
>> > be able to use what you learn with both. This will not help you with
>> > T-SQL
>> > specific commands, however. So, yes, Firebird will help you, but not as
>> > much
>> > as working in SQL Express.
>> >
>> Allright, good to know!
>> Thanks you!
>>
>>
>>