Object size query

2009-04-21 Thread Mark Devine
I would like to query the DB for any stored objects  1GB.  The output will
help improve our incl/excl specifications.

The only table/column I see is CONTENTS/FILE_SIZE.  My select works, but
obviously it's an intense scan.

Is CONTENTS the only place?  Please suggest the best approach.


Re: Object size query

2009-04-21 Thread Remco Post

On Apr 21, 2009, at 18:09 , Mark Devine wrote:


I would like to query the DB for any stored objects  1GB.  The
output will
help improve our incl/excl specifications.

The only table/column I see is CONTENTS/FILE_SIZE.  My select works,
but
obviously it's an intense scan.

Is CONTENTS the only place?  Please suggest the best approach.



contents and backups, and yes, you don't want to run queries against
those


--
Met vriendelijke groeten,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622


Re: Object size query

2009-04-21 Thread Richard Sims

You can produce an allied report by scanning your dsmaccnt.log to
report on large adds (Archive or Backup operations) over a long period
of time, by dividing quantity of data sent to the TSM server by the
number of objects, allowing you to identify nodes and users (but not
filespaces) involved in biggies.  This alone may be sufficient for
your needs; or you might use it to perform a more limited Select on
formidable tables.

   Richard Sims


Re: Object size query

2009-04-21 Thread Gee, Norman
Not really an answer, set max file size of primary pool to 1GB and force
it to a next large file pool.  Check what files ends up in the large
file pool. 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: Tuesday, April 21, 2009 10:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Object size query

You can produce an allied report by scanning your dsmaccnt.log to
report on large adds (Archive or Backup operations) over a long period
of time, by dividing quantity of data sent to the TSM server by the
number of objects, allowing you to identify nodes and users (but not
filespaces) involved in biggies.  This alone may be sufficient for
your needs; or you might use it to perform a more limited Select on
formidable tables.

Richard Sims


Re: Object size query

2009-04-21 Thread Conway, Timothy
Upgrade to version 6, and just run your SQL without fear. :) 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mark Devine
Sent: Tuesday, April 21, 2009 10:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Object size query

I would like to query the DB for any stored objects  1GB.  The output
will help improve our incl/excl specifications.

The only table/column I see is CONTENTS/FILE_SIZE.  My select works, but
obviously it's an intense scan.

Is CONTENTS the only place?  Please suggest the best approach.