Here is a head scratcher for you.
Reports->Project->History->Time sheets
You are on the server and select any time sheet and click Print. The 35+ pages will print to the screen in about 45 seconds.
Now, if you are the only person in GP and run the exact same report on a workstation for the same time sheet you get the exact same performance.
However, if anyone else logs into GP and does not even do anything, it will take over 30 minutes for the same report to appear on the screen.
On the server it does not matter if someone else is in GP.
What could possibly be causing such a discrepancy?
I agree that it seems strange that just being logged in would cause the performance issue that you are seeing. Maybe you can enable a SQL profile trace and see what events either have longer durations of time passing, or have more calls being made, when you compare both scenarios. Hopefully that will give you some things to pursue further.
It is only this report. They enter a lot entries per timesheet which explains the 45 pages. No modifications have been made to this report. I do not see the connection between having no one else in GP and having someone just sitting on their homepage.
Hi Richard,
Is this issue only occurring on this Project Timesheet History report, or are you able to reproduce the same performance issue on any report (i.e. any project reports) or does this just occur on this report? Does it occur on any other non project related reports as well? Are you using the canned report or is this report modified? Just trying to help to narrow down further what else could be coming into play.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,524 Super User 2024 Season 2
Martin Dráb 228,469 Most Valuable Professional
nmaenpaa 101,148