Al least in the last TSM symposium it was planned for TSM 6.1, due in
last quarter of 2008, to migrate the propietary database to DB2 getting most
of its characteristics, such as online db reorganization.

It will also get a real SQL interface instead of the abstraction layer it
provides
now.

Not related, but interesting in my opinion, was the introduction of
deduplication
in the backup strategy.

On 8/8/07, Richard Sims <rbs AT bu DOT edu> wrote:
>
> On Aug 8, 2007, at 9:20 AM, Llano, Martin wrote:
>
> > Somebody knows if now IBM recommends to migrate to Oracle the TSM
> > database when it is too great? In affirmative case, exists some
> > tech note that it indicates how make the migration?
>
> The product has historically utilized its own, proprietary database:
> there is no current provision for utilizing a commercial database for
> TSM itself.  Where the database has grown too large for its
> activities to fit within daily schedules utilizing best technologies,
> relief is gained by implementing a new server instance with a fresh
> database, to either start taking on new client implementations or to
> receive exports from the old server.
>
>     Richard Sims
>