"Vic Polotsky" wrote:

> Manish: have you run any SQL trace on your SPs? We have a similar problem,
> and the trace shows that when a rteport is run, the same SP starts and stops
> several times. However, when a report is generated, the result data set is
> correct. When we cut & pasted the query into a report, it also was executed
> several times. Does anyone know how Reporting Services run queries and SP?
>
> "manish" wrote:
>
> > I am not running the report just calling the same SPs by selecting reporting
> > enviornment's dataset and passing the parameters..There is no report
> > rendering here. Still it takes longer. Can there be anything to verify?
> >
> > I ran this query on query analyser pointing to the same DB, report points to
> > but it errors out by not identifying executionlog & catalog. Is it a
> > different DB I should point to?
> >
> > "Christopher Conner" wrote:
> >
> > > You can verify the timing by looking at the logging - in query analyzer,
> > > change the database to the reportserver DB then do the following:
> > >
> > > select ca.name, el.timedataretrieval, el.timeprocessing, el.timerendering
> > > from executionlog el
> > > inner join catalog ca on (el.reportid = ca.itemid)
> > > where name = 'NAME OF REPORT'
> > >
> > > We use this all the time to check up on long running queries, or to see if
> > > the performance is related to the RENDERING of the report as opposed to
> > > actual data being retrieved from SQL.
> > >
> > >
> > > =-Chris
> > >
> > > "manish" <manish@discussions.microsoft.com> wrote in message
> > > news:35634A1F-DC0B-423F-B101-90ABD0EF75BA@microsoft.com...
> > > >I have 3 SPs those when run on query analyzer, runs within 1-3 secs. But
> > > >when
> > > > the same is run in data window of RS, doesnt return atleast before 2 mins
> > > > each. When the report is run , it shows "report is running" for a long
> > > > time
> > > > before it returns sometimes.
> > > >
> > > > This is very critical for us, Some Pz advise...
> > >
> > >