You’re offline. This is a read only version of the page.
312
Hi Team,
It's an reporting issue, As per RDP Based Resport, currently we are using the table type as Inmemory.
But, currently we are facing the performance issue on this report I.e while opening the rerport some times got a performance issue meand not opended and throwing an exception.
So, I have to decide for Debug. As per report debuggin only on 'DPProcess/DPprocessTmpDB' classes and I extended the 'DPProcessTmpDB' instead of DPbase class because TmpDB type can accept here.
As per the flow, I have changed the table type -> TmpDB In table property.
my concern is coding means we have to write the method 'linkPhysicalTableInstance()'.
Please see the above one, they were using SETTmp() Mthod. This will store into the client/server. for debugging where to call this method 'linkPhysicalTableInstance() ?
Note: my concern is, get resolved the issue to change the TMPDB.
For debugging we must call this method 'linkPhysicalTableInstance(), pleaese help me on this.
Thanks,
Vinay.
Hi,
if you want to change the table type to TempDB, you could check almost any standard report in the system that is using a temp table, and see how they are handled in the report class.
For example BankAccountStatementTmp.
Thanks for your reply, we are running the report 7 -8 times + per time.
Each time data storing into the in-memory (basically using for less amount of data) into the client/server means will be stuck there. This will be the cause so, we want to change as Tempdb ( will be storing into the db means handling large volume of data).
Regarding the performance issues, generally we will use the 'dppreprocesstmpdb' class for this I want to change to tempdb.
I hope you knows right diff between in-memory and tempdb.
Thanks,
Vinay.
Hi vinilkumar,
How did you determine that the type of the temp table is the cause for your performance issue? I recommend you to first make sure that you understand the cause of the issue, before starting to refactor things that are possibly not relevant at all.
What exception did you get when running the report?
Here's my suggestion: put back your original code, but comment out the line that inserts to temp table. Now the report is obviously empty, but you can see whether it still takes a long time to load. If it still takes a long time to load, then the temp table type has nothing to do with your issue.
Most likely the performance issue is caused by the code that you use to populate the temp table (fetching a lot of data from many places, possibly with inefficient code).
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (