Re: Question on dbspaces and third party repositories

If you ever only want to recover one of the databases, but leave the other databases active to the users, the yes it does. Since you can only restore at a dbspace level, if you mix all the databases the same dbspace and, for example, some "bozzo programmer" drops a table by accident in one databases, then your whole system is dead while you recover the whole lot. If each database is in its own dbspace then only the users of the affected datase will be dead until the database is recovered. How will the third party recover your data and only affect minimal users otherwise? As per another post on here they would need a second server of similar disk space to the production serever to load the whole database onto and then unload and restore the affected data. Geezer From The Freezer <Geezer@Freezer.com> wrote in message news:<406D3A55.A70184BD@Freezer.com>... > scottishpoet wrote: > > > > Not sure what your backup strategy is like, but it is possible to > > recover indivual dbspaces. > > > > Therefore if you have each database in a different dbspace it meansyou > > can recover a particular database. > > > > Geezer From Freezer <Geezer@Freezer.com> wrote in message news:<4069394D.22B03164@Freezer.com>... > > > We have an old system that I have inherited that has several repositories on > > > some > > > some third party software that is stored in informix. > > > Each repository is stored in an individual dbspace. What is the reason for this, > > > and > > > would there be any reason (performance or admin) for not having the repositories > > > stored > > > on one dbspace? > > All restores and backups are done by the third party-software - therefore does > it matter > about storing individual databases in seperate dbspaces?