Burst or Schedule

[vinu_rnr]

Hi All
Would like to know from Resource Consumption/load at cognos server,  which one is better Bursting or Scheduling


have a report which needs to be distributed to 10 people. ( only their data in report).

1 ) can create the view and hard code the filter and schedule it to each individual

2)  Can create create burst key ( again hard code the email here) as neither we have emails readily available in db nor distriubtion list groups  (  can have all these set up but needs time)

Infrastructure:-
Cogons: 10.2.1
DB back-end : oracle 11g, star schema datawarehouse
Output:  MS Excel 2007,  file size per person  will be ~10MB
Report execution time is 2-3 mins ( when executed for single person filters)





many thanks in advance,

[New_Guy]

Hi,

If the set up is not done for bursting and if it is only for 10 people, go for scheduling with reportviews.

Good luck
New guy

[vinu_rnr]

Hi,
thank you for the response.

although i might go for 'Report Views' now eventually wish to move to Bursting, as the number of people is expected to reach 30+.
Definitely 'Report View' is inefficient as numbers will grow and people keep on changing.


Right now i wish to know from server resource consumption point of view , which is expensive? Bursting or Scheduling? and how?

[MFGF]

Hi,
thank you for the response.

although i might go for 'Report Views' now eventually wish to move to Bursting, as the number of people is expected to reach 30+.
Definitely 'Report View' is inefficient as numbers will grow and people keep on changing.


Right now i wish to know from server resource consumption point of view , which is expensive? Bursting or Scheduling? and how?

Hi,

Bursting and scheduling are two different concepts. Bursting is taking a single report and generating multiple outputs from it, based around defined burst grouping values. Scheduling is the automated execution of reports at specific times. A burst report can be scheduled to run, as can a non-burst report. Alternatively a burst report can be run manually, as can a non-burst report.

I suspect what you are asking here is which is more efficient, a burst report returning 10 outputs or running a report 10 times with different prompt or filter values?

If so, it's probably pretty even each way. The burst report will most likely fire the reporting queries 10 times as it runs. Running a report 10 times will result in the same - the reporting queries being run 10 times. Each will have a similar amount of rendering to do.

Cheers!

MF.

[vinu_rnr]

Good Evening MF,

thanks for reply,   yes, you are right i was of interested which one is efficient. i got you are point. :)
have a nice day ahead.

Cheers,
Vinu

[vinu_rnr]

Morning MF,

just a follow-up question here surrounding "The burst report will most likely fire the reporting queries 10 times as it runs"

here you meant say  that report queries will hit the db as  many times as the number of burst key (per my question it is supposed to be 10)?   
I was of impression that cognos will fetch a huge data set from db and starts segmentation at cognos  end based on burst key? am i wrong here? 

[MFGF]

Morning MF,

just a follow-up question here surrounding "The burst report will most likely fire the reporting queries 10 times as it runs"

here you meant say  that report queries will hit the db as  many times as the number of burst key (per my question it is supposed to be 10)?   
I was of impression that cognos will fetch a huge data set from db and starts segmentation at cognos  end based on burst key? am i wrong here?

Hi,

Generally bursting works like a master/detail relationship would work, and usually results in queries being fired to the database multiple times - once for each burst grouping value.

Cheers!

MF.