Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Temp Table in Memory -...
Microsoft Dynamics GP (Archived)

Temp Table in Memory - Dexterity 8.0

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

We have a legacy application developed in Dexterity 8.0. J Yes, it’s bit old. It is crashing while we are trying to fill a Memory temp table.  (around 500K rows. ) It doesn’t given any exception but just crashes. Here is the some of the information we get.

 Fault Module Name:    CTPMEM32.dll
  Fault Module Version:    1.1.0.1
  Fault Module Timestamp:    416f0269
  Exception Code:    c0000005
  Exception Offset:    00001e8b
  OS Version:    6.1.7601.2.1.0.18.10
  Locale ID:    3081

Changing the memory table to SQL memory table makes it super slow. Not sure what are the other options we have if loading data in temp is necessary ?

*This post is locked for comments

  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,928 Most Valuable Professional on at
    RE: Temp Table in Memory - Dexterity 8.0

    Hi Himal

    I see you said you are caching on demand now.

    So you cache after a the first read rather than pre-loading?  That should be faster if you are only hitting a small number of the records.

    David

  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,928 Most Valuable Professional on at
    RE: Temp Table in Memory - Dexterity 8.0

    Hi Himal

    Why are you loading 500K records into a temporary table? That must take ages and is not efficient.

    Just create the table as a permanent SQL table with the keys you need. That should be much less work to create and maintain and can be shared by multiple users.

    David

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Temp Table in Memory - Dexterity 8.0

    Hi David,

    Thanks for your reply. Yes, end up converting Cache all to Cache as required. Which is more efficient and fast. We are  planning to upgrade to Dex 16 and that task just sitting there in the queue and we keep fixing other critical client issues. :(

    Hope the day come soon.

    Regards,

    Himal

  • Verified answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,928 Most Valuable Professional on at
    RE: Temp Table in Memory - Dexterity 8.0

    Hi Himal

    That is too many rows for a memory temp table.

    Memory tables are no longer implemented in memory, instead they are using a folder in the user's temp folder.

    However, in Dexterity 8.0 it might still be trying to use memory. For it to work in memory it needs a large contiguous block of memory. If it runs out of memory (ie, block of memory used up even if machine still has more ram) it crashes. This is why they changed to use ctree tables in a folder under the temp folder instead.

    Why do you need that much data in a temp table? Surely there must be a better way.

    Also why are you on Dexterity 8.0.... Dex 16.0 is out.

    David

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans