Highly skilled software engineers are working on a complex code base making our beloved database engine snapier with each release and the grants from the FF ensures that the people can continue to contribute their skills. A lot of new features, performance enhancements and many more things make our database development life easier without paying any license fees to deploy the Firebird server, even in commercial projects.
Development on the Firebird code base is not free. It costs money. Money, the Firebird Foundation as a non-profit organization tries to generate via Foundation membership subscriptions and sponsoring. But, international money crisis has drastically shortened the prospect of sustaining the project into the second half of 2009.
Currently there are ONLY 158 paid-up members. An unbelievable small number compared to the number of downloads of the Firebird binaries each month. Even if each download would generate e.g. 1 Euro back to the Foundation, the Foundation would not be in the current situation.
We have to react fast. We have to react NOW. If you have any interest in helping to ensure the Firebird project can keep development going next year then you need to sit down right now, relax for a few minutes and ask yourself:
- Are you making profit by using the Firebird engine for free?
- What would be the cost for migrating to another database engine, in case Firebird won't be there anymore?
I'm pretty sure over 300 USD which is the current price of an annual Foundation voting membership subscription. So, think again:
- Does your business rely on Firebird?
If yes, you really should, or even better, you MUST think about supporting the Firebird project in a financial way. Even if it is just one percentage of your revenue based on the usage of Firebird is fine. Each cent counts.
Think again ... And then go to the Firebird Foundation site.
Thanks,
Thomas
(Co-founder of the Firebird Foundation in 2002)
[ 1 comment ] ( 15 views ) | permalink |
( 2.9 / 229 )The Firebird Transaction Statistic Logger (FTSL) utility is now available as Freeware without source code. You can download the utility here.
If you have any feedback, feel free to contact me.
Enjoy,
Thomas
[ 4 comments ] ( 46 views ) | permalink |
( 2.8 / 280 )Hello,
the 6th International Firebird Conference 2008 in Italy will start today. I didn't make it this year, but make sure to read Martijn's blog to get updated what's going on.
Cheers,
Thomas
[ add comment ] ( 2 views ) | permalink |
( 2.8 / 161 )Due to the 8th anniversary of our LogManager series, there is a 50%
discount on all our LogManager products.
Our LogManager series is a proven logging/auditing suite supporting
InterBase, Firebird, MSSQL, Advantage and NexusDB, used by customers in
over 40 countries.
More details on our 2 weeks promo is available here:
http://www.upscene.com/lm_party_promo.htm
Thomas
[ add comment ] ( 16 views ) | permalink |
( 2.8 / 136 )I was in need getting a trace of executed MDX and SQL statements when Mondrian is processing a user request, e.g. via the JPivot based web application as shown here.
Firebird 2.1 does have monitoring tables, but querying them will give you a snapshot of what's going on at this time. What I wanted is to have a real trace to see, e.g.:
* What SQL statements Mondrian has executed against my database
* Are aggregate tables used or not
There is a way to enable MDX/SQL tracing in Mondrian, but, again, it isn't really fool-proof documented how to do that. I've asked in the Mondrian forum about that. You will find the ultimate solution here.
Now, for a particular executed MDX statement, I get the following log file entry:
2008-09-11 15:59:54,956 DEBUG [mondrian.mdx] 10: with member [Measures].[Operation Mode] as 'IIf(([Measures].[Average Operation Mode] = 1.0), (- 1.0), IIf(([Measures].[Average Operation Mode] = 2.0), 1.0, IIf(([Measures].[Average Operation Mode] = 3.0), 0.0, 0.0)))'
select NON EMPTY {[Measures].[Operation Mode], [Measures].[Average Operation Mode]} ON COLUMNS,
NON EMPTY Hierarchize(Crossjoin({[Customer].[All Customers]}, Union(Union(Crossjoin({[Date].[All Dates]}, {[Time].[All Times]}), Crossjoin({[Date].[All Dates]}, [Time].[All Times].Children)), Crossjoin({[Date].[All Dates]}, [Time].[All Times].[11].Children)))) ON ROWS
from [EodOlap]
2008-09-11 15:59:54,956 DEBUG [mondrian.sql] 45: SqlTupleReader.readTuples [[Date].[(All)], [Time].[Minute]]: executing sql [
select
"DIM_TIME"."DIM_TIME_HOUR" as "c0",
"DIM_TIME"."DIM_TIME_MINUTE" as "c1"
from
"DIM_TIME" "DIM_TIME",
"FACT_MEASURED_VALUE" "FACT_MEASURED_VALUE"
where
"FACT_MEASURED_VALUE"."DIM_TIME_ID" = "DIM_TIME"."DIM_TIME_ID" and
("DIM_TIME"."DIM_TIME_HOUR" = 11)
group by
"DIM_TIME"."DIM_TIME_HOUR",
"DIM_TIME"."DIM_TIME_MINUTE"
order by
"DIM_TIME"."DIM_TIME_HOUR" ASC,
"DIM_TIME"."DIM_TIME_MINUTE" ASC
]
2008-09-11 15:59:54,956 DEBUG [mondrian.sql] 45: , exec 0 ms
2008-09-11 15:59:55,003 DEBUG [mondrian.sql] , exec+fetch 47 ms, 55 rows
2008-09-11 15:59:55,019 DEBUG [mondrian.mdx] 10: exec: 63 ms
Nice. Very nice.
Thomas
[ add comment ] ( 7 views ) | permalink |
( 3 / 251 )
Calendar
