| Description |
I am wondering if this has anything to do with the issue we were seeing with the GL by Account ID Detail report.
[~greg.marcom] ran some tests to see the source of the issue, and it looks like the query for recalcing the summary table is taking up quite a bit of resources.
Here is info from Greg's Analysis:
"The following query displays the top 10 procedures that use the most memory and disk IO on your system. The query further breaks down the logical vs physical reads. Physical reads are the ones that actually touch the disk, logical reads are the ones that read from memory. The ones that read from disk more often will be the ones that are most likely executed less. Fixing the following queries will most likely alleviate your server’s resources quite a bit.
!pastedImage_d46529_0.png! {color:#1f497d}We have a customer that is experiencing major slowness, even 10 mins after reboot.{color}
{color:#1f497d}I ran some simple queries, you can see one below, and think it might have something to do with i21 GL.{color}
{color:#1f497d} {color}
{color:#1f497d}I have the SQL server on the customer system limited to 16GB. After a reboot and 3 people get logged into system, the SQL server spikes to 16GB and the software becomes really slow. But I don’t see the slowness moving around the server.{color}
{color:#1f497d} {color}
{color:#1f497d}I also noticed that the tempdb is huge compared to irely01:{color}
!pastedImage_d46529_1.png! {color:#1f497d}It looks like these queries are writing to the tempdb, I wonder if this could be an issue that tempdb is reaching some limit?{color}
{color:#1f497d} {color}
{color:#1f497d}There is also a document on the desktop for the server called “controlled login.rft” that the customer created after a fresh reboot. They talk about what they are doing after they login and who is logged in."{color}
{color:#1f497d}{color}
Let me know what you guys think.
|