|Informix Application Development - Getting Started|
|IBM Informix Developer's Handbook|
|Embedding IBM Informix|
Archive - Jul 2010
If you're following along with my posts on installing, initializing, adding space and creating databases and tables in Informix then you're ready to start doing some basic performance tuning. You can improve performance dramatically by making some simple changes to the ONCONFIG and bouncing the engine. The first and most important change to make is to increase Buffers, this is where Informix will be caching all of the data you are reading in from disk.
This article is written in English and Portuguese
Este artigo está escrito em Inglês e Português
Chat with the Labs: Post End of Service Support Options and Upgrade Best practices / Opções de suporte após fim de serviçoSubmitted by fnunes on July 30, 2010 - 18:13
This article is written in Portuguese and English
Este artigo está escrito em Português e Inglês
Andrew Ford already announced this in his blog, so for the English version I'll just recommend that you check his article. Basically there will be a very important Chat with the labs session on August 26. For all the customers still in version 9.40 and v10, this may really make a difference.
The next Informix Chat With The Labs has been scheduled for Thursday August 26, 11:30 AM Eastern Time.
Join in and listen to Albert Martin (Director, WW Data Management Support), Charles Gonsalves (Sr. Manager, WW Informix Support), Ron Privett (Sr. Engineer, Americas Down Systems and Diagnostics Team) and Chris Fender (Program Director, WW IM S&S Strateger and Sales) talk about your support options after your Informix version reaches End of Service and the best practices for upgrading to a new version of Informix.
Or as IBM puts it:
I guess at some point you'd like to actually create a database and create some tables with indexes to hold some data. This logging and backup stuff is fun and all, but what good is a database without data? We know that you put database objects in dbspaces and we have 2 of those already, the rootdbs and llogdbs01, but we don't want to put our data in these dbspaces. If we have multiple disks at our disposal we would put the chunks that make up these dbspaces on different disks to minimize I/O contention and increase parallelism, we would want to do the same thing with our dbspaces that hold
There have been questions from multiple posters on the Informix Forums lately asking about Journaled File Systems (JFSes) like EXT3, EXT4, and ZFS among others. Bottom line? JFSes should NEVER be used for storing data for a database system. ANY database system, whether it is Berkley DB, Oracle, Sybase, DB2, MySQL, PostGreSQL, MS SQL Server, Informix, whatever. "But", you protest, "the journaling makes the filesystem safer. It speeds recovery. It is 'good thing'!" No. Not for databases. Flat out - no!