> >> We evaluated SQL Server X for our embedded engine rejected it
> >> because:
> >>
> >> - The database size has been crippled to 2G
> >> - The installer requires .NET (and installs it).
> >> - The footprint is 50G
> >
> > How much?
>
> Yes, 50Gbytes. But the hands-down winner was Oracle XP weighing in
> at a CD-busting 600+Gb!

Do you see the difference between MB and GB ?

...

> >> - Full set of built in functions with correct NULL handling (unlike
> >> FB...)
> >
> > Examples of failures in Fb? I'm just curious.
>
> Just about every UDF that ships with FB seems to assume that NULL ==
> 0.

Sure ?

> Round, Sign, Sin, you name it. So for our calculations, we have
> to wrap each one in a
>
> (CASE WHEN arg is NULL THEN CAST(NULL AS result_type) ELSE func(arg)
> END)
>
> which I am sure wreaks havoc on any indexing we may have defined.
>
> (Gotta love those typed NULLs too...)

Do you heard about BY DESCRIPTOR parameters ?
May be you want to take a look on supplied fbudf library ?

...

> BTW, If I am wrong about this and there IS an easy fix. I'd love to
> know about it. I have a major work item coming up in the next 6
> months to deal with this issue and I am not looking forward to it...
> (And if any developer wants to send me an estimate on what it would
> take to add this, I'd be very interested in looking at it.)

Ask Adriano for this

Regards,
Vlad