More academic hype about the Semantic Web
A major Semantic Web researcher has built a cluster that can do RDF queries, and hence can get subsecond response time on queries against a database of 7 billion three-column records, The Register obsequiously reports. Golly gee whiz wow.
“The importance of this breakthrough cannot be overestimated,” said Professor Stefan Decker, director of DERI.”
I actually think the Semantic Web contains some good ideas, but this kind of over-the-top breathlessness doesn’t seem to do anybody very much good.
| Categories: RDF and graphs | 3 Comments |
IBM’s mid-range OLTP offering gets strengthened
In the past, when I’ve asked Jeff Jones of IBM for permission to post one of his well-written notes, his response has pretty much been “Of course! Why did you bother asking?” So this time I’m just going ahead and skipping that step. The note is about IBM’s mid-range flavor of DB2, targeted directly at MySQL.
Today, IBM announced that its popular DB2 9 Express-C software is now available with an optional low-cost yearly support subscription. DB2 Express-C has been available without license charges for downloading, application development, deployment and redistribution since January 2006. It remains available without license charges for those that do not require support. Electronic general availability of the new support option is scheduled for June 1, 2007.
The new DB2 Express-C support option provides 24×7 product support, regular fixpacks and upgrade protection. In addition, this option provides support for high availability clustering, offsite disaster recovery, and data replication with remote data servers without additional charge.
Background
— Subscriptions are priced at $2,995 (U.S.) per server per year. This is identical to MySQL Enterprise Gold, but DB2 Express-C includes features not found in MySQL including pureXML support, high availability clustering (MySQL Cluster support costs extra), autonomic features, and no-charge administration and development tools. Unlike the free offerings from Microsoft and Oracle, DB2 Express-C does not place limits on the size or number of databases managed. With up to 4 GB of memory and up to 2 processors, DB2 Express-C can run on more powerful servers, can scale higher and can perform faster than its competitors. Read more
| Categories: IBM and DB2, Mid-range, MySQL, OLTP | Leave a Comment |
You can now listen to and watch the midrange OLTP DBMS webinar
The replay of last Wednesday’s webinar is now available at this link. It will probably stay up for 3-6 months. There may also be a more persistent link to the audio part only, which I will supply if and when I get it.
The main subject was what kinds of features differentiate OLTP DBMS, and for what kinds of applications you should care about them. As an introduction I spelled out some of my thoughts on what kind of overall DBMS product portfolio enterprises should and do have.
| Categories: EnterpriseDB and Postgres Plus, Mid-range, OLTP | Leave a Comment |
Progress Software progress report
For the past 20+ years – all the way back to when it was still privately held — I’ve periodically gotten up to speed on Progress Software. I’m trying again now, and to that end dropped by yesterday for a chat with Jeff Stamen. I’ll give a brief overview now – which is probably all I’m qualified to do right now anyway – and then loop back with more detailed info after I get it.
After a reorganization at the beginning of this (November) fiscal year, the vast majority of Progress’ products fall into one of five buckets, which I shall glibly refer to in decreasing order of size as “Progress Classic,” “SOA,” “drivers,” “memory-centric,” and “EasyAsk.” Here’s a quick overview of each. Read more
| Categories: Companies and products, Mid-range, Object, OLTP, Progress, Apama, and DataDirect | 3 Comments |
More on Cast Iron Systems
I chatted again recently with Simon Peel of Cast Iron Systems, and this time I got a better understanding of Cast Iron’s simplicity claim. It refers largely to a drag-and-drop interface that furthermore provides default mappings between pairs of application suites. Simon bristled a bit when I referred to this as mapping “like to like,” because he’s proud that it’s a little smarter than that. Still, “like to like” seems to be what it typically amounts to — customers go to customers, customer addresses go to customer addresses, and so on. Read more
MySQL/IBM — will everybody please calm down?
Reuters wrote a really stupid article on the MySQL/IBM deal, and some bloggers have gotten over-excited as well. Even the not-ignorant among these seem to be overlooking one or more of the following points:
- The IBM/MySQL deal is just for the iSeries.
- The iSeries is the successor to the AS/400 and System 38, and thus is in a decades-old family of machines that have some weirdnesses in their DBMS support.
- In particular, DB2 on the iSeries isn’t the same thing as DB2 on other boxes, although multiple DB2s do at least nominally run there.
So while it’s interesting and nice, this deal isn’t that relevant to IBM’s mainstream software business at all.
Read more
| Categories: IBM and DB2, Mid-range, MySQL, OLTP, Open source | 4 Comments |
The big ANTs secret is officially out
ANTs has now put out a press release saying what was already obvious — the company is offering middleware to run applications written for one DBMS over another backend instead. The ANTs folks fondly think their own engine is just as good as anybody else’s, but realistically customers prefer name-brand DBMS for persistent storage, so that’s what they’re offering.
Read more
And then there is FileMaker
Chris Kubica of Application Architects, LLC is a big FileMaker fan. And there are of course reviews and articles that agree with him, although when FileMaker sponsored this white paper they did not choose an author famed for the independence of his analysis.
So should FileMaker be included on my list of midrange OLTP DBMS or not?
| Categories: FileMaker | 20 Comments |
Free webinar on midrange OLTP/multipurpose DBMS, sponsored by EnterpriseDB
At noon Eastern Time on Wednesday, April 25, I’ll be doing a webinar about midrange OLTP/multipurpose DBMS, sponsored by EnterpriseDB, who not coincidentally are purveyors of same. You can sign up here.
Below is some of EnterpriseDB’s verbiage promoting the event. I particularly like the part where they refer to me as a “renowned industry guru.” 😉
The DBMS market, once thought to be an oligopoly, is experiencing some refreshing disruption – thanks to open source-based databases that are proving viable alternatives to traditional, more costly incumbents. Whether you’re trying to control database costs or support new application development, there’s never been a better time to reevaluate your database platform strategy.
But, how can you realistically compare alternatives like MySQL and EnterpriseDB against established database platforms like Oracle, DB2, and SQL Server?
Let your applications be your guide.
In this webcast, renowned industry guru Curt Monash provides an objective context in which to evaluate and select the right DBMS based on your application’s needs. He’ll discuss how all DBMS’ features are not all created equal in the way they address application-specific demands. Particular focus will be given to the unique requirements of transaction-intensive applications.
Join us for this eSeminar and learn how to:
- Go beyond the typical feature checklists of self-proclaimed “enterprise-class” offerings to provide a more in-depth barometer of a DBMS’ true capabilities
- Define the DBMS platform requirements for a variety of transaction-intensive applications
- Delineate between must-have and nice-to-have DBMS features for your application
| Categories: EnterpriseDB and Postgres Plus, Mid-range, OLTP | 2 Comments |
SolidDB and MySQL 5.0 – how industrial-strength in OLTP?
MySQL 4.0 is an OLTP joke. MySQL 5.0, however, shows a lot of progress in terms of real transactions, foreign keys, referential integrity, triggers, stored procedures and so on. In anticipation of the MySQL user conference next week, I got a quick briefing from Paola Lubet and Murat Demiroglu at Solid Information Technology, whose SolidDB is one of the two transactional storage engines for MySQL (the other is InnoDB, now owned by Oracle).
The layer provided by MySQL actually does most of what I think of as “language processing” – parsing, optimization, drivers, triggers, stored procedures, referential integrity, etc. SolidDB is a storage engine providing actual execution. Its features and virtues include:
• Online backup. (Note: Apparently, the extra-cost InnoDB online backup product isn’t showing up on price lists these days.)
• Optimistic (as well as pessimistic) concurrency control. This can be a good performance feature for applications that have a whole lot of Adds and very few Changes.
• General reliability. Unless they really botched the port, Solid benefits from a long history of very reliable operation.
• High availability. Scheduled for alpha in early summer and beta in the fall is a high-availability option. This initial-release will be master-slave synchronous replication. More sophisticated replication could come later on, as could memory-centric performance, if market conditions seem to warrant it (I’m betting they will).
| Categories: Mid-range, MySQL, OLTP, Open source, solidDB | 2 Comments |