05-17-2017 12:44 AM - edited 05-17-2017 11:24 AM
jhadfield, (Just corrected name with right person intended)
After ACT opened DB started at 118MB and SQL at 451MB.
SQL Server reached 794MB in 40 min. while in Oppt doing Lookup's, Omit records in list view, jumping between Oppt & Contact Records, and deleting some Oppt Records. It's all about doing multiple lookups then omit or lookup selected.
1st try from contact list view and Detail view with 20,000 looked up out of my 76,000 did in this order but memory did not zero out and it took a few min. before Cancel stopped. Even after closing ACT! its process goes away but SQL Server Win NT 64 bit does not change in what memory it holds.
File | Export- Text Delimited |Bullet Contact Records and Current lookup | Tab and checked Yes, export names. | all fields in Map | hit finish then after 30 sec. hit Cancel.
05-17-2017 01:01 AM
Not sure if this will help - we have 6 pc's running Act!. The 2 newest ones (purchased in the last 9 months) are the ones experiencing ' out of memory' issues.
05-17-2017 08:23 AM
1st screenshots of before & after File>Export>Cancel process are attached. Laptop was rebooted at 10am and this is about 80 minutes later. Haven't touched the ACT V19 app and Memory usage has doubled in 3 minutes.
Act! Premium Version 188.8.131.52, Update 2
05-17-2017 09:41 AM
2nd before & after (File>Export>cancel) Screenshots about 90 minutes later are attached
05-17-2017 11:45 AM
I replied with my results to your earlier post with File | Export | Cancel steps. I now see you really just do three clicks and I not a drawn out export.
I confirmed ACT.exe memory usage drops, but I don't need to wait an hour. You can do multiple Lookup's like starting with all Contacts then do Omit's and other lookup by value in a field to see ACT usage grow. A faster way to max out how much memory ACT/SQL takes is doing import data into massive number of contact records (60,000), and fields (60). Then doing for a while lookups and omits in Contact List view, or in Oppt Table delete records or even lookup and omit from the list to see Red X or lockup ACT.
I think there is a second issue with SQL Server memory used. It does not shrink after F| E |C and I noticed performance hit and or see the RED X?
My trick to release memory SQL takes (which max out around 2GB) yet even with ACT still running is open SQL Server Configuration Manager, go to services, right click on SQL Server (ACT7) and do Restart.
05-18-2017 08:34 AM
05-18-2017 12:35 PM
Do you need for me to supply more screenshots? The APP has not crashed since I've been following the File>Export.cancel process every 80-90 minutes
05-18-2017 01:30 PM
Since your working an a patch I would point out during testing to keep eye on SQL Server Memory. When it reaches 2GB and never exceeds it and ACT.exe is only few 100MB I have noticed Red X as well or ACT just hangs. So push the imports or lookups I spoke of to quickly get to the 2GB max.