Singleton

[gshilpa24]

Hi,

I have singleton used in one of my report. Can anybody let me know if there is another alternative way to drag an item other than singleton?

Thanks,

[blom0344]

That is why singletons were introduced in version 8.3 (I believe). To be used at any place within a report. Specifically for that purpose..

[MFGF]

So true, Blom :) To answer the original question, there *are* other ways to do this. You could associate a query with the report page and drop an item onto the page. You could perhaps use a repeater rather than a singleton (for a single value). You could use a list (for a single value) and hide the headers and borders. Being honest, though, singletons make life easier than any of these other techniques.

I always call refer to a Singleton as a Valerie. Those who know me well will testify that my jokes are always awful, and often terrible :) To get this particular joke, you need to be British, more than 45 years of age, and a Blue Peter fan :)

MF.

[blom0344]

I like the way you spell 'Blom'   ;)

[gshilpa24]

Thank you for the reply. The concern is to check which one would increase the performance of the report. which one is feasible to use?
List or SIngleton or table cells.

Thanks,

[blom0344]

I doubt you will find a difference in performance..

[gshilpa24]

ok , Thank you.

[Gopinath]

I doubt you will find a difference in performance..

Blom,

My understanding is that, eventhough I have 1 query in my report and if I use a singleton(without checking all data items in 'Properties' property of the singleton) to display a data item from the query, cognos creates 2 different query internally(1 for singleton and the other for datacontainers in the report) .

Won't this degrade the report performance?

Expecting your valuable reply.

[blom0344]

A singleton is meant to return ONE row and ONE dataitem. It's use totally differs from normal data queries. In normal cases you can therefore not 'reuse' the dataquery where you would need the singleton. Report performance depends not just on the effectiveness of queries, but also on possible local processing; layout , rendering etc

[Lynn]

...

I always call refer to a Singleton as a Valerie. Those who know me well will testify that my jokes are always awful, and often terrible :) To get this particular joke, you need to be British, more than 45 years of age, and a Blue Peter fan :)

MF.

Well a quick google search helped me figure out the Valerie reference and might one day serve me well if I find myself involved in a pub quiz  8)

As for the performance question, I think a query that is referenced in more than one layout will result in more than one call to the database with the appropriate minimized SQL based on the data items referenced in each container.

To Blom's point, I would suggest a query be created specifically for your Valerie, err, I mean singleton, that is constructed to run optimally for it's purpose.

[MFGF]

Well a quick google search helped me figure out the Valerie reference and might one day serve me well if I find myself involved in a pub quiz  8)

Good detective work there! For a star prize, what were the names of the other two on the show at the same time? :)

To Blom's point, I would suggest a query be created specifically for your Valerie, err, I mean singleton, that is constructed to run optimally for it's purpose.

Yes - I concur.

MF.

[Lynn]

Good detective work there! For a star prize, what were the names of the other two on the show at the same time? :)

Fred PromptMany and Christopher Crosstab?

[MFGF]

Fred PromptMany and Christopher Crosstab?

Sigh. I can tell Christmas is coming. Have they started putting whisky in the tea at work? :)

[blom0344]

Sigh. I can tell Christmas is coming. Have they started putting whisky in the tea at work? :)

whiskey, no doubt

[MFGF]

whiskey, no doubt

Doh! Drattd kyboard!! ;)