|
|
You're in the
sql server reporting services
group:First Time Delay on client systems
sql server reporting services:
Microsoft: I've just set up a SQL Reporting Services server. All seems to be working fine, however I've noticed that when a report is opened from a user system accessing the report server for the first time, the report takes a very long time to open (a few minutes in some cases), and sometimes I have to abort it and start again. This is a report that should take a couple of seconds at most. Once the report does finally open, it opens fine from then on, even when refreshed, or run by different parameters. Also all other reports availale to the user also run fine after that first one finally opens. There are no errors, just the Report is being generated message. It's like the server has to get aquainted with the machine accessing it the first time.... Again, once the report has run, this problem goes away. I have tested this on around 10 different user systems, with the same results on all of them, some are Win2k, some are XP. The report server is running on a dual processor, clean install Server 2003, SQL Server 2000 sp 3a. So far it appears to be machine, rather than user account, related... Any assistance would be greatly appreciated. I'm holding off a full on roll out of this until I get this solved, as it will certainly drive users crazy. Thanks, TomT
Hi Tomt,
Thanks for your posting! From your descriptions, I understood that you would like to know why there will be a delay (a few minutes in some cases) when you first time access Reports. Have I understood you? Correct me if I was wrong. Based on my konwledge, this is Reporting Services by design behavior. The first user who runs the report with a unique region code creates a cached report that contains data for that region. Subsequent users who request a report using the same region code get the cached copy. create that report will cost a lot of time. The report server caches reports based on report execution options. Execution options determine whether a report is cached and the length of time it stays in cache. After some number of minutes or at a scheduled time, the cache is emptied. The cache stays empty until a new report execution operation occurs and a new copy of the report is cached. Thank you for your patience and corporation. If you have any questions or concerns, don't hesitate to let me know. We are always here to be of assistance! Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Michael,
I'm not sure what you mean by region code.... What I'm seeing is for example: I open a report on my system, which has previously accessed the report server and experience no delay. I go to another system, which has never accessed that server, and run the same report, and get a delay of up to a few minutes. Hope that is clear... Thanks for your help, Tom [quoted text, click to view] "Michael Cheng [MSFT]" wrote:
> Hi Tomt, > > Thanks for your posting! > > From your descriptions, I understood that you would like to know why there > will be a delay (a few minutes in some cases) when you first time access > Reports. Have I understood you? Correct me if I was wrong. > > Based on my konwledge, this is Reporting Services by design behavior. The > first user who runs the report with a unique region code creates a cached > report that contains data for that region. Subsequent users who request a > report using the same region code get the cached copy. create that report > will cost a lot of time. > > The report server caches reports based on report execution options. > Execution options determine whether a report is cached and the length of > time it stays in cache. After some number of minutes or at a scheduled > time, the cache is emptied. The cache stays empty until a new report > execution operation occurs and a new copy of the report is cached. > > Thank you for your patience and corporation. If you have any questions or > concerns, don't hesitate to let me know. We are always here to be of > assistance! > > > Sincerely yours, > > Michael Cheng > Microsoft Online Partner Support > > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. >
I'm sure he meant report query parameters and region code was the specific
one in his head for an example. -- Cheers, '(' Jeff A. Stucker \ Business Intelligence www.criadvantage.com -------------------------------------- [quoted text, click to view] "TomT" <tomt@newsgroup.nospam> wrote in message news:FC1995F8-D81D-4049-87EC-4B88A4DDB8BB@microsoft.com... > Michael, > > I'm not sure what you mean by region code.... > > What I'm seeing is for example: I open a report on my system, which has > previously accessed the report server and experience no delay. I go to > another system, which has never accessed that server, and run the same > report, and get a delay of up to a few minutes. > > Hope that is clear... > > Thanks for your help, > > Tom > > "Michael Cheng [MSFT]" wrote: > >> Hi Tomt, >> >> Thanks for your posting! >> >> From your descriptions, I understood that you would like to know why >> there >> will be a delay (a few minutes in some cases) when you first time access >> Reports. Have I understood you? Correct me if I was wrong. >> >> Based on my konwledge, this is Reporting Services by design behavior. The >> first user who runs the report with a unique region code creates a cached >> report that contains data for that region. Subsequent users who request a >> report using the same region code get the cached copy. create that report >> will cost a lot of time. >> >> The report server caches reports based on report execution options. >> Execution options determine whether a report is cached and the length of >> time it stays in cache. After some number of minutes or at a scheduled >> time, the cache is emptied. The cache stays empty until a new report >> execution operation occurs and a new copy of the report is cached. >> >> Thank you for your patience and corporation. If you have any questions or >> concerns, don't hesitate to let me know. We are always here to be of >> assistance! >> >> >> Sincerely yours, >> >> Michael Cheng >> Microsoft Online Partner Support >> >> When responding to posts, please "Reply to Group" via your newsreader so >> that others may learn and benefit from your issue. >> ===================================================== >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >>
Ok, thanks. If that is the case, that is not the situation I'm talking about,
it seems to be related to whether or not a system has ever accessed the server at all, there are no delays on systems that have, regardless of parameters. Thanks [quoted text, click to view] "Jeff A. Stucker" wrote:
> I'm sure he meant report query parameters and region code was the specific > one in his head for an example. > > -- > Cheers, > > '(' Jeff A. Stucker > \ > > Business Intelligence > www.criadvantage.com > -------------------------------------- > "TomT" <tomt@newsgroup.nospam> wrote in message > news:FC1995F8-D81D-4049-87EC-4B88A4DDB8BB@microsoft.com... > > Michael, > > > > I'm not sure what you mean by region code.... > > > > What I'm seeing is for example: I open a report on my system, which has > > previously accessed the report server and experience no delay. I go to > > another system, which has never accessed that server, and run the same > > report, and get a delay of up to a few minutes. > > > > Hope that is clear... > > > > Thanks for your help, > > > > Tom > > > > "Michael Cheng [MSFT]" wrote: > > > >> Hi Tomt, > >> > >> Thanks for your posting! > >> > >> From your descriptions, I understood that you would like to know why > >> there > >> will be a delay (a few minutes in some cases) when you first time access > >> Reports. Have I understood you? Correct me if I was wrong. > >> > >> Based on my konwledge, this is Reporting Services by design behavior. The > >> first user who runs the report with a unique region code creates a cached > >> report that contains data for that region. Subsequent users who request a > >> report using the same region code get the cached copy. create that report > >> will cost a lot of time. > >> > >> The report server caches reports based on report execution options. > >> Execution options determine whether a report is cached and the length of > >> time it stays in cache. After some number of minutes or at a scheduled > >> time, the cache is emptied. The cache stays empty until a new report > >> execution operation occurs and a new copy of the report is cached. > >> > >> Thank you for your patience and corporation. If you have any questions or > >> concerns, don't hesitate to let me know. We are always here to be of > >> assistance! > >> > >> > >> Sincerely yours, > >> > >> Michael Cheng > >> Microsoft Online Partner Support > >> > >> When responding to posts, please "Reply to Group" via your newsreader so > >> that others may learn and benefit from your issue. > >> ===================================================== > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> > >
Thanks Jeff, that was my thread, I believe, which I started over because of
profile issues - and to get MS involved. Unfortunately, that solution is not applicable to the problem I am describing, apparently not very well....:-) Here's a clearer scenario (I hope): I run report A on my system, it opens immediately (my system has run reports previously, not necessarily report A, however). I goimmediately to another system , which has never run any reports at all, and run report A. In many (although not all) cases, minutes will pass before the report processing is competed. Since the time between running the report on one system and the other is miniscule, I don't think the process is unloading - there appears to be something else going on... [quoted text, click to view] "Jeff A. Stucker" wrote:
> Look for an earlier thread on this topic. Bruce and others have invented a > keep-alive type solution that periodically runs a trivial report on schedule > to keep the process from unloading. > > -- > Cheers, > > '(' Jeff A. Stucker > \ > > Business Intelligence > www.criadvantage.com > -------------------------------------- > "TomT" <tomt@newsgroup.nospam> wrote in message > news:FACEA9F4-41FE-4C02-AD27-8FB118FB73AB@microsoft.com... > > Ok, thanks. If that is the case, that is not the situation I'm talking > > about, > > it seems to be related to whether or not a system has ever accessed the > > server at all, there are no delays on systems that have, regardless of > > parameters. > > > > Thanks > > > > "Jeff A. Stucker" wrote: > > > >> I'm sure he meant report query parameters and region code was the > >> specific > >> one in his head for an example. > >> > >> -- > >> Cheers, > >> > >> '(' Jeff A. Stucker > >> \ > >> > >> Business Intelligence > >> www.criadvantage.com > >> -------------------------------------- > >> "TomT" <tomt@newsgroup.nospam> wrote in message > >> news:FC1995F8-D81D-4049-87EC-4B88A4DDB8BB@microsoft.com... > >> > Michael, > >> > > >> > I'm not sure what you mean by region code.... > >> > > >> > What I'm seeing is for example: I open a report on my system, which has > >> > previously accessed the report server and experience no delay. I go to > >> > another system, which has never accessed that server, and run the same > >> > report, and get a delay of up to a few minutes. > >> > > >> > Hope that is clear... > >> > > >> > Thanks for your help, > >> > > >> > Tom > >> > > >> > "Michael Cheng [MSFT]" wrote: > >> > > >> >> Hi Tomt, > >> >> > >> >> Thanks for your posting! > >> >> > >> >> From your descriptions, I understood that you would like to know why > >> >> there > >> >> will be a delay (a few minutes in some cases) when you first time > >> >> access > >> >> Reports. Have I understood you? Correct me if I was wrong. > >> >> > >> >> Based on my konwledge, this is Reporting Services by design behavior. > >> >> The > >> >> first user who runs the report with a unique region code creates a > >> >> cached > >> >> report that contains data for that region. Subsequent users who > >> >> request a > >> >> report using the same region code get the cached copy. create that > >> >> report > >> >> will cost a lot of time. > >> >> > >> >> The report server caches reports based on report execution options. > >> >> Execution options determine whether a report is cached and the length > >> >> of > >> >> time it stays in cache. After some number of minutes or at a scheduled > >> >> time, the cache is emptied. The cache stays empty until a new report > >> >> execution operation occurs and a new copy of the report is cached. > >> >> > >> >> Thank you for your patience and corporation. If you have any questions > >> >> or > >> >> concerns, don't hesitate to let me know. We are always here to be of > >> >> assistance! > >> >> > >> >> > >> >> Sincerely yours, > >> >> > >> >> Michael Cheng > >> >> Microsoft Online Partner Support > >> >> > >> >> When responding to posts, please "Reply to Group" via your newsreader > >> >> so > >> >> that others may learn and benefit from your issue. > >> >> ===================================================== > >> >> This posting is provided "AS IS" with no warranties, and confers no > >> >> rights. > >> >> > >> >> > >> > >> > >> > >
Look for an earlier thread on this topic. Bruce and others have invented a
keep-alive type solution that periodically runs a trivial report on schedule to keep the process from unloading. -- Cheers, '(' Jeff A. Stucker \ Business Intelligence www.criadvantage.com -------------------------------------- [quoted text, click to view] "TomT" <tomt@newsgroup.nospam> wrote in message news:FACEA9F4-41FE-4C02-AD27-8FB118FB73AB@microsoft.com... > Ok, thanks. If that is the case, that is not the situation I'm talking > about, > it seems to be related to whether or not a system has ever accessed the > server at all, there are no delays on systems that have, regardless of > parameters. > > Thanks > > "Jeff A. Stucker" wrote: > >> I'm sure he meant report query parameters and region code was the >> specific >> one in his head for an example. >> >> -- >> Cheers, >> >> '(' Jeff A. Stucker >> \ >> >> Business Intelligence >> www.criadvantage.com >> -------------------------------------- >> "TomT" <tomt@newsgroup.nospam> wrote in message >> news:FC1995F8-D81D-4049-87EC-4B88A4DDB8BB@microsoft.com... >> > Michael, >> > >> > I'm not sure what you mean by region code.... >> > >> > What I'm seeing is for example: I open a report on my system, which has >> > previously accessed the report server and experience no delay. I go to >> > another system, which has never accessed that server, and run the same >> > report, and get a delay of up to a few minutes. >> > >> > Hope that is clear... >> > >> > Thanks for your help, >> > >> > Tom >> > >> > "Michael Cheng [MSFT]" wrote: >> > >> >> Hi Tomt, >> >> >> >> Thanks for your posting! >> >> >> >> From your descriptions, I understood that you would like to know why >> >> there >> >> will be a delay (a few minutes in some cases) when you first time >> >> access >> >> Reports. Have I understood you? Correct me if I was wrong. >> >> >> >> Based on my konwledge, this is Reporting Services by design behavior. >> >> The >> >> first user who runs the report with a unique region code creates a >> >> cached >> >> report that contains data for that region. Subsequent users who >> >> request a >> >> report using the same region code get the cached copy. create that >> >> report >> >> will cost a lot of time. >> >> >> >> The report server caches reports based on report execution options. >> >> Execution options determine whether a report is cached and the length >> >> of >> >> time it stays in cache. After some number of minutes or at a scheduled >> >> time, the cache is emptied. The cache stays empty until a new report >> >> execution operation occurs and a new copy of the report is cached. >> >> >> >> Thank you for your patience and corporation. If you have any questions >> >> or >> >> concerns, don't hesitate to let me know. We are always here to be of >> >> assistance! >> >> >> >> >> >> Sincerely yours, >> >> >> >> Michael Cheng >> >> Microsoft Online Partner Support >> >> >> >> When responding to posts, please "Reply to Group" via your newsreader >> >> so >> >> that others may learn and benefit from your issue. >> >> ===================================================== >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> rights. >> >> >> >> >> >> >>
Hi Tom,
What kind of credentials are used against the datasource? Each IE and IIS do some hand shaking on the first request. It is also possible that domain authentication or the first connection to the data source lead to this kind of delay. Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Michael,
Thanks for your response. It does appear to be related to the user. I logged onto a system which had never accessed the report server, and got the report right away. I then had another person log on to the same machine, and he got a delay. I am using a shared data source to access the actual sql server data, so that is common to everyone, in other words the authentication for the reports to the sql server data is not specific to individual users, their credentials are not used. I wonder if the IIS server (which is the same machine as the Report Server) is a factor in the delay? People can get to the server without delays, it just happens when they run their first report.... [quoted text, click to view] "Michael Cheng [MSFT]" wrote:
> Hi Tom, > > What kind of credentials are used against the datasource? > Each IE and IIS do some hand shaking on the first request. It is also > possible that domain authentication or the first connection to the data > source lead to this kind of delay. > > > Sincerely yours, > > Michael Cheng > Microsoft Online Partner Support > > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > >
Hi Tom,
Sorry for the delay as this issue really seems to be strange. Does report manager respond quickly? To find out the root cause of this issue we may need to analyze IIS and network package deeply, this work has to be done by contacting Microsoft Customer Service and Support. Therefore, we probably will not be able to resolve the issue through the newsgroups. If the issue is urgent, I recommend that you open a Support incident with Microsoft Customer Service and Support so that a dedicated Support Professional can assist with this case. For a complete list of Microsoft Customer Service and Support phone numbers, please go to the following address on the World Wide Web: http://support.microsoft.com/directory/overview.asp Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Michael,
Thanks for your reply. Report manager does respond quickly, as do the reports once a user has accessed the report server one time. I gather you have not heard about this issue from anyone else? Thanks, Tom [quoted text, click to view] "Michael Cheng [MSFT]" wrote:
> Hi Tom, > > Sorry for the delay as this issue really seems to be strange. > > Does report manager respond quickly? > > To find out the root cause of this issue we may need to analyze IIS and > network package deeply, this work has to be done by contacting Microsoft > Customer Service and Support. Therefore, we probably will not be able to > resolve the issue through the newsgroups. If the issue is urgent, I > recommend that you open a Support incident with Microsoft Customer Service > and Support so that a dedicated Support Professional can assist with this > case. > > For a complete list of Microsoft Customer Service and Support phone > numbers, please go to the following address on the World Wide Web: > http://support.microsoft.com/directory/overview.asp > > > Sincerely yours, > > Michael Cheng > Microsoft Online Partner Support > > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. >
Hi Tom,
Yes, I contacted our SRS development team and they do not have much experience on this kind of issue. To further troubleshooting this issue, I believe it will be better to make some survey about your scenario directly and this work has to be done by our PSS services. That's why I would like to suggest you contacting them. Thank you for your patience and corporation. If you have any questions or concerns, don't hesitate to let me know. We are always here to be of assistance! Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |