"Forgosh, Seth" wrote:
> Does anyone have an idea of a non-painfull way to dump the CONTENTS table to
> another DB? Anytime I need to use that table it puts a huge strain on the
> TSM server. Thanks in advance.
Being that the results of a Q CONTENT command comes from the TSM
database, there is no way to "dump" the portion of the database that is
accessed when you use the Q CONTENT command.
The CONTENT command stresses the TSM server because it pulls a large
percentage of the database's content to display results. If you want to
access the TSM database without using TSM itself, try connecting to the
database via ODBC and your favorite database frontend (mySQL, Access,
whatever).
--
Mark Stapleton ([EMAIL PROTECTED])
