death knell for Informix
Posted in 2007
Not a technical support thread: a poster forwarded a Computerworld article about IBM and MySQL AB enabling MySQL on System i (AS/400), with DB2 for i acting as a certified MySQL storage engine, framing it as bad news for Informix. Respondents (including IBM staff) rebutted the premise, noting IDS doesn't run on iSeries so the announcement has nothing to do with Informix. The discussion then drifted into a side argument about whether DB2 accepts "SELECT 1+2" without a FROM clause (it needs sysibm.sysdummy1 or the standard VALUES statement). No problem to resolve.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Installation, Setup & Upgrades, Licensing & Editions
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9017838 IBM to open its midrange systems to MySQL's database April 25, 2007 (Computerworld) -- SANTA CLARA, Calif. -- MySQL AB and IBM announced Wednesday that users of the latter's System i hardware line will be able to run the MySQL open-source database on the midrange servers. The System i version of IBM's DB2 database, which is integrated with the midrange line's operating system as a standard feature, will serve as a certified storage engine for MySQL, the two companies said at MySQL's annual user conference here. MySQL claims that its namesake database is being used in 11 million active installations worldwide. The software is based on a modular architecture that lets users swap in different storage engines tuned for different application scenarios. Companies that use the System i -- better known by its original AS/400 name, and then as the iSeries -- will gain the advantage of being able to implement online and transactional MySQL applications while continuing to store data in DB2, according to the two vendors. The agreement to combine the technologies "is about opening up new applications to old data and old applications to new data," said Mike Smith, IBM's chief software architect for the System i line. "I think it's an interesting and potentially excellent deal for both sides," said Stephen O'Grady, an analyst at Denver-based consulting firm RedMonk. "IBM gets access to the more or less ubiquitous MySQL platform with its DB2 storage engine, and MySQL gets an opening to the still popular [System i] platform." DB2 is one of the three leading relational databases used by large enterprises, along with Oracle and Microsoft Corp.'s SQL Server. But MySQL's low cost of ownership and rapid rise in popularity has led to the creation of a larger ecosystem of supporting software for the open-source database than is currently available for DB2. In addition, MySQL is making inroads into the installed bases of the top database vendors. For example, one-third of the 269 Oracle users who responded to an e-mail survey conducted last June for the Independent Oracle Users Group said that they also use MySQL (download PDF). IBM also agreed to sell service and support subscriptions for the MySQL Enterprise database via its reseller network and the System i sales team. That should help MySQL, which is preparing for an initial public offering, to gain more paying customers. During his keynote speech on Tuesday, MySQL CEO Marten Mickos said that his company has just one paying user for every thousand nonpaying ones. In another effort to increase its count of paying customers, MySQL in January announced a site license that lets companies deploy as many MySQL databases as they want for a flat fee of $40,000 per year. That price, Mickos claimed, is roughly comparable to the cost of one single-processor Oracle server license. The MySQL Enterprise Unlimited offering has attracted users such as ESPN Inc., The New York Times Co. and TransUnion LLC, according to MySQL. Mickos said that in this year's first quarter, the company doubled the number of MySQL Enterprise subscriptions sold compared with the same period last year. MySQL recently also updated a remote network monitoring service, rolled out last fall, that can scan all of the database servers behind a customer's firewall, check to see if they're set up correctly and then provide advice on how to make them adhere to best practices. Mickos said that can "take away the black-box feel that servers sometimes have and help you implicate or exonerate the database when an application is not running well."
On Wed, 25 Apr 2007 20:35:33 -0400, "Data Cruncher" <datacruncher4@yahoo.com> wrote: >http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9017838 > > >IBM to open its midrange systems to MySQL's database > >April 25, 2007 (Computerworld) -- SANTA CLARA, Calif. -- MySQL AB and IBM >announced Wednesday that users of the latter's System i hardware line will >be able to run the MySQL open-source database on the midrange servers. >The System i version of IBM's DB2 database, which is integrated with the >midrange line's operating system as a standard feature, will serve as a >certified storage engine for MySQL, the two companies said at MySQL's annual >user conference here. Since when did IFMX run on the AS/400 platform? News to me . . . JWC
Data Cruncher wrote: > http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9017838 > > > IBM to open its midrange systems to MySQL's database What does that have to do with IDS? IDS doesn't run on iSeries. There are exactly 2 things at work here: 1. Enabling of mySQL on iSeries (good for iSeries) 2. Enabling of mySQL directly on DB2 for iSeries (without dependency on another storage engine) (still good for iSeries) Depending how one reads the articles one may suspect that IBM will provide soem help to get mySQL closer to the SQL Standard. I sure would love to see mySQL users stop nagging: DB2 is bad because "SELECT 1+2" returns an syntax error ... ;-) Cheers Serge -- Serge Rielau DB2 Solutions Development IBM Toronto Lab
Serge Rielau wrote: ... > I sure would love to see mySQL users stop nagging: DB2 is bad because > "SELECT 1+2" returns an syntax error ... ;-) ... Hmmm - I am confused: C:\\>db2 connect to sample Database Connection Information Database server = DB2/NT 9.1.3 SQL authorization ID = DB2ADMIN Local database alias = SAMPLE C:\\>db2 select 1=2 from sysibm.sysdummy1 SQL0104N An unexpected token "=" was found following "select 1". Expected tokens may include: ",". SQLSTATE=42601 C:\\>db2 select 1+2 from sysibm.sysdummy1 1 ----------- 3 1 record(s) selected. Jan M. Nelken
Serge Rielau wrote: ... > I sure would love to see mySQL users stop nagging: DB2 is bad because > "SELECT 1+2" returns an syntax error ... ;-) ... Hmmmm, I seem to be confused again: C:\\>db2 connect to sample Database Connection Information Database server = DB2/NT 9.1.3 SQL authorization ID = DB2ADMIN Local database alias = SAMPLE C:\\>db2 select 1+2 from sysibm.sysdummy1 1 ----------- 3 1 record(s) selected. Jan M. Nelken
Jan M. Nelken wrote:
> Serge Rielau wrote:
>
> ...
>> I sure would love to see mySQL users stop nagging: DB2 is bad because
>> "SELECT 1+2" returns an syntax error ... ;-)
> ...
>
> Hmmmm, I seem to be confused again:
>
> C:\\>db2 connect to sample
>
> Database Connection Information
>
> Database server = DB2/NT 9.1.3
> SQL authorization ID = DB2ADMIN
> Local database alias = SAMPLE
>
> C:\\>db2 select 1+2 from sysibm.sysdummy1
>
> 1
> -----------
> 3
>
> 1 record(s) selected.
$ db2 "select 1+2"
SQL0104N An unexpected token "END-OF-STATEMENT" was found following "select
1+2". Expected tokens may include: "<table_expr>". SQLSTATE=42601
MySQL accepts this crap because they don't have the standardized VALUES
statement.
--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany