I’m glad to report that we’ve just released a new version of DB2, namely DB2 Express-C 9.7.2. This version — of what is arguably the most advanced hybrid database system in the world — is (as usual) absolutely free to develop with, deploy in production, and even redistribute.
Unlike SQL Server Express which is limited to 10GB of data, there are no data limits with DB2 Express-C. This means no database size limits or any restrictions on the number of databases, connections, users, etc…
Oracle XE is even more restrictive than SQL Server Express and seriously insecure, having not been updated for a long time despite the presence of major security vulnerabilities. Unlike Oracle XE, DB2 Express-C uses the same core code as its commercial editions and is always kept up-to-date.
In case you are wondering, there’s no catch. We generate our revenue from affordable, but entirely optional, dedicated 24/7 technical support (a popular business model in the open source community). If you haven’t tried DB2 Express-C before or you currently have an older version installed, consider getting the latest one here and taking it for a spin.
What’s new
Some of the improvements and features of this FixPack 2 edition include:
Possibly related posts:
If you enjoyed this post, then make sure you subscribe to my Newsletter and/or Feed.
I sincerely welcome and appreciate your comments, whether in agreement or dissenting with my article. However, trolling will not be tolerated. Comments are automatically closed 15 days after the publication of each article.
HI Antonio,
I guess (and am afraid) that you’re tired of this question but I just have to ask:
Is the Mac OS X branch of IBM DB2 V9 dead now? Any hope to see a post-9.5 version
Cheers and best wishes,
—Torsten
Hi Torsten,
DB2 on Mac is definitely not dead, however it might be proceeding at a slower pace than we’d hoped. I’m not sure about the details, but I’ll try to see if there is a way to speed up the process.
I was wondering about DB2 on the Mac also.
Thanks a lot, Antonio! Highly appreciated.
—Torsten
Hi Antonio,
Somewhat off-topic, but since you seem to be a voice for the Python/Ruby folks at IBM, any idea if there will be effort put into getting the SqlAlchemy dialect up to par with the current SqlAlchemy release? It’s terribly out of date, and the existing version does not implement limits or offsets via the ROW_NUMBER() OVER() workaround used in the Django/Rails adapaters.
Glad to see offsets finally supported in SQL
I’ll see what I can do about this.
Much appreciated. As it stands, the SA dialect hasn’t seen an update since November 2008. Business-wise, it would be a huge help to know if there will be future updates and if so, when they can be expected (roughly), or if the project is going to be retired completely in favour of the more prominent Django adapter.
Hi Antonio,
> Support for the MySQL syntax for LIMIT and OFFSET
This is a good news !
I tried “SELECT * FROM EMPLOYEE LIMIT 4″ with DB2 9.7 FP2 , but I got a SQL0104N error.
I couldn’t find descriptions about LIMIT or OFFSET keyword at DB2 information center.
Could you tell me pre-requirement to use LIMIT/OFFSET ?
Thank you.
Hi Akira,
please try the following:
Hi Antonio,
It works!
Thank you very much.
This MySQL processing mode is optimized for fast fetching, fetching is very fast.
Using where rownum between X and Y is still not optimized and it is slow.
I would like to see supported SQL standard syntax OFFSET skip ROWS, because core engine is already in.
[...] Fixpack for DB2 9.7. This also includes a variety of useful enhancements that you can read about in Antonio’s blog and DB2 Express-C team [...]
The release information states “There is improved support for Python-DB2 applications.” Is there more to this statement than better Django 1.2.1 support? I cannot find any specifics in the release information. Thanks in advance