The sysadmin database: version 11
Do most people move this new system db that is created in the rootdbs by default in version 11? For those folks that do not move it, what are you seeing as far as sizing goes for the rootdbs? I am used to not placing anything else within the rootdbs so I am exploring the pro's and cons of just adding more space to our existing rootdbs (and how much to add to accomodate the sysadm db) versus moving it to a new space after initial creation Thanks Tom
It is strongly recommended to move the sysadmin database once you have other dbspaces set up. Especially if you do not disable the statistical data collection that is on by default. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) See you at the 2010 IIUG Informix Conference April 25-28, 2010 Overland Park (Kansas City), KS www.iiug.org/conf Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Wed, May 5, 2010 at 3:56 PM, Tom Lehr <tomcaml@gmail.com> wrote: > Do most people move this new system db that is created in the rootdbs > by default in version 11? > For those folks that do not move it, what are you seeing as far as > sizing goes for the rootdbs? > I am used to not placing anything else within the rootdbs so I am > exploring the pro's and cons of just adding more space to our existing > rootdbs (and how much to add to accomodate the sysadm db) > versus moving it to a new space after initial creation > > > Thanks > Tom > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >
We create a special dbspace just for sysadmin and move it in there. It becomes a critical dbspace, so using a regular data dbspace adds to risk. If you loose a chunk within this data dbspace, and then want to bring the engine back online leaving the chunk down, if sysadmin is in that dbspace you can't do it - engine toast. Jarrod Teale MES Team Lead Fonterra NZ -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Tom Lehr Sent: Thursday, 6 May 2010 7:57 a.m. To: informix-list@iiug.org Subject: The sysadmin database: version 11 Do most people move this new system db that is created in the rootdbs by default in version 11? For those folks that do not move it, what are you seeing as far as sizing goes for the rootdbs? I am used to not placing anything else within the rootdbs so I am exploring the pro's and cons of just adding more space to our existing rootdbs (and how much to add to accomodate the sysadm db) versus moving it to a new space after initial creation Thanks Tom _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/