Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+SQL\s+queries\s+and\s+TSM\s+Server\/platform\s+performance\s+measurement\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] SQL queries and TSM Server/platform performance measurement (score: 1)
Author: David McClelland <David.McClelland AT REUTERS DOT COM>
Date: Wed, 25 Jul 2007 16:47:59 +0100
Hi Guys, Every now and then I come across a SQL query and a benchmark such as the following which purports to be useful in high-level performance problem spotting. For example: select activity, cast(
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-07/msg00288.html (13,033 bytes)

2. Re: [ADSM-L] SQL queries and TSM Server/platform performance measurement (score: 1)
Author: Dave Canan <ddcanan AT ATTGLOBAL DOT NET>
Date: Wed, 25 Jul 2007 14:39:55 -0700
I'd like to comment on these queries, being as I was the one who originally submitted that technote to the IBM database. First, the queries are a little old, and they were recently revised to higher
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-07/msg00297.html (14,525 bytes)

3. Re: [ADSM-L] SQL queries and TSM Server/platform performance measurement (score: 1)
Author: Wanda Prather <wprather AT JASI DOT COM>
Date: Wed, 25 Jul 2007 14:32:43 -0500
I don't understand the relevance of the pgs per hour query on Expiration. My understanding from an STE presentation is that TSM doesn't necessarily walk all the pages in the DB during expiration; it
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-07/msg00298.html (14,303 bytes)


This search system is powered by Namazu