Release 1.1.01 is recommended to every user, especially those still using Beta versions.

The main change you will notice is the option to minimize to the notification area.

When minimized this way, Sinatica Monitor displays new alarms as message baloons.

This feature was one of the most requested during Beta and is very aligned to the Sinática Monitor proposal of monitoring your database while you work on something else and alerting you only when something extraordinary happens.

Although if you prefer the previous way of minimizing, you just have to disable this option in the new User Options screen.

You may read the release notes for the complete list of fixes and changes and if you have any questions or suggestions please contact me.

Download Sinática Monitor for Firebird release 1.1.01 now.

Along with the new Sinática Monitor 1.1 comes the new Sinática Online Store.

And please don’t forget our ongoing promotions:

• Discount to Beta Users. (it ends in less than one week!)
• Discount to members of the Firebird Foundation.

If you have any questions regarding Sinática or Sinática Monitor, email me.

I really believe that one of the ways to a stronger Firebird Foundation is by creating opportunities for members to receive benefits from their memberships. A stronger Foundation means a stronger Firebird, and that is to everyone’s benefit.

With that spirit in mind, and with much joy, today I announce that Sinática will give a 10% discount to all members of the Firebird Foundation.

If you wish to buy Sinática Monitor, email me your name and membership number (here). I will reply with the discount coupon you can use on the Sinática Online Store.

The conditions:

• You or your company must be a member of the Firebird Foundation
• Your subscription payments must be up-to-date (here)
• This discount is not available in conjunction with any other promotional offerings

In addition, there is no problem if you are not currently a member. You can join now and receive the discount in just a few days.

If you have any questions, please email me and I will respond immediately.

You may answer this survey about your experience with Sinática Monitor Beta and get a 20% discount in case you decide to buy the commercial version.

If you’re not using Sinática Monitor yet, download it now.

Here’s how the discount works:

• Use Sinática Monitor Beta for a few days until you’re familiar with it.
• Answer the survey and don’t forget to register a valid email address.
• The survey will be online starting today until 11/25/08.
• By the end of this period I’ll send a promotional code to each participant’s email.
• This code may then be used to get the 20% discount in the Sinática Online Store.
• The Beta Discount will be valid until 01/25/09.

The survey has 21 questions and takes about 3 minutes to be answered.

It’s called Sinática Monitor for Firebird. And it was specially created to monitor your database and discover those hard-to-find problems.

And that’s just the beginning.

Visit out new site and see screenshots of Sinática Monitor in action.

Sinática Monitor is entirely free during the Beta period.

Download now and find out what it can do for your database.

And please don’t be shy! I want to hear from you. Send me your ideas and suggestions!

I have no idea who came up with this day but I loved it. And here’s what I propose to spread the meme:

Send <your favorite gift> to yourself at work.

When someone asks, say:

- Oh, today is Programmer’s Day and <your beloved one> remembered me.

Let’s make this day and the greatness of our work known to all. Or better let’s make it a national holyday. Or better yet, let’s make it a world-wide holyday! After all we are prefectionists.

You can attach the profiler to catch the deadlock event and see the actual commands that are deadlocking. I did that, and found there was always one particular SQL command involved:

UPDATE [Posts]
SET [AnswerCount] = @p1, [LastActivityDate] = @p2, [LastActivityUserId] = @p3
WHERE [Id] = @p0

If it detects a deadlock, SQL Server forces one of the deadlocking commands to lose — specifically the one that uses the least resources. The statement on the losing side varied, but in our case the losing deadlock statement was always a really innocuous database read, like so:

SELECT *
FROM [Posts]
WHERE [ParentId] = @p0

To fix the problem they had to instruct MS SQL Server to use dirty reads on each those selects. What kept hammering my head all these days was not how can modern databases still block readers. But the lesson we can take from the episode. Independently of server and its architectural limitations, the important thing is to understand it and also to know your application’s environment very well.

In the case of StackOverflow Jeff found that a possible solution was dirty reads. If the transactions performed by the website took a long time, dirty reads would not be an option. But knowing his application very well he knew that was not the case. Choosing dirty reads would have no consequences. Independently of what ACID purists would say. And I confess I turned my nose when I first read "dirty read".

Thanks to its multi-generational architecture Firebird does not block readers. So it’s natural that this problem may seem strange to us. But each architecture has its pros and cons. This same multi-generational architecture, if not correctly used, can be a problem. It’s the case of long running transactions or "stuck transactions".

Such transactions cause record versions to accumulate in the database. (These versions can also be called generations. It’s multi-generational architecture, remember?) The more versions accumulate more work Firebird has to do to find the correct version of each record. If stuck for long enough Firebird server can get slow to the point of looking like it’s dead. How much time depends of the database load and the server’s hardware. Could be a month, could be an hour.

I’ve seen it happen many times. In some of those occasions I saw managers argue for hours that MS SQL Server or Oracle don’t have such problem. The fact is that they have other architectural details that you must take into account in your application. For example, some databases block readers. Simply switching databases, as some of those managers suggested, is not a solution.

Although having StackOverflow powered by Firebird would not be a bad idea. ;)

Since Firebird 2.1 forced-writes also work in linux. With that in mind I put together a comparison between the two modes.

What are forced-writes and when to use them?

I hope DBAs who like to live dangerously find this useful.

Great question!

The Product is made for Firebird database users. Programmers and database administrators.

Although I won’t say much more about it for now (including it’s name, that’s why we’ll just call it The Product) I can already tell you that next week The Product will have its first chance to leave the lab and work in a production environment.

So stay tuned for more Firebird articles and news on The product here at Sinática blog.

Arriving at the Unimep Theater

I learned a few new tricks and left with a very good perspective about the project’s future. This perspective I now share with you.

Firebird 3.0

We can wait a hybrid based on ClassicServer but with good doses of code from both SuperServer and Vulcan. And that’s good. No huge changes that would take decades to stabilize. The Firebird team’s proposal, according to Dmitry Yemanov, is evolutionary and not revolutionary.

Very early in the morning there was a lot of people already.

Dmitry Yemanov also showed strong opinions about having shared data and metadata caches. It seems ClassicServer’s dedicated cache is going to be deprecated very soon. Amen.

Installation and configuration will be easier with only one executable for all architectures.

In the MasterClass I had the opportunity to express how much I like the monitoring tables and how easier they make the life of a Firebird DBA. The good news is that it seems the Firebird team is also interested in extending them.

I was the last one to leave! :)

Firebird 4?

When I asked about a native SQL parser, Dmitry Yemanov said it is very interesting for Firebird and it’s in the plans. But there is no schedule and he can’t make promises.

Internally Firebird translates SQL into a recursive language called BLR. Statements are then executed in BLR. In theory a native SQL parser would bring a slight performance increase. Most importantly, it would make extending Firebird’s SQL syntax a much simpler task.

The same goes to having value distribution histograms in indices. No schedule.

Meetings

Another fantastic part of FDD was meeting and getting to know our Russian colleagues Dmitry Kuzmenko (IBSurgeon), Dmitry Yemanov (Firebird SQL) e Michael Phlippenko (Fast Report). And also some of the Speakers as Alexandre Benson Smith (Thor Software), o Professor Beto (Unimep) e o Luis Paulo (Chamando.com.br).

None of that would be possible, of couse, without the folks at Firebase.com.br. A Big Thanks to them and in special to Carlos Cantu for organizing this event.

See you next year!

This unimep terminal speaks for me.

Good Night. Waiting automatic energy shutdown in a few moments.