Business

The future of Sybase

Well I am a few months late on the news, but I see that Sybase is now part of SAP.
I spent a number of years as a Sybase developer, and it was kind of sad to see the slow slide against its competitors like Microsoft and Oracle. I’m not sure there is much they can do around Sybase ASE. It has lost most of its foothold in financial markets, but I still have the occasional discussion with recruiters about working with Sybase, one as recently as this week. I avoid all discussion about working with the Sybase 4GL PowerBuilder.
The database advantage that Sybase still has is in the embedded device market, which shows no sign of stagnating.

Standard
Software Development

Using MySQL stored procedures

A lot of my past software development background has been around client/server in financial markets, with the main RDBMS use in Sybase, but also MS SQL Server and Oracle. In most cases stored procedures is the way to query and manipulate the database. There are a number of reasons for this including security, performance and centralised business logic out of the client.
Now in recent years I have made the move to web development in PHP, and in most cases using MySQL as the database server. From personal experience of others code, and available FOSS systems, it is extremely rare to see use of MySQL stored procedures behind web sites. They are there, have been for a number of years, and do work. So why is this so?
The first reason I could understand, was that they are a MySQL 5 feature, and most FOSS apps set their MySQL minimum requirements at version 4.x.
I now understand a 2nd and crucial reason, thanks to a post by Jay Pipes. MySQL stored procedures are not the same as Sybase or MS SQL. The shared compilation performance benefit is not there in MySQL 5.0/1 for non persistent or pooled connections. ie. most smaller to medium web sites. Their usage may actually be to the detriment of performance.
So stored procedures can have a use in MySQL, but mostly in limited use cases.

Standard