Microsoft Access and ECC RAM
Hello - I would like to get some feedback regarding the importance of ECC RAM when developing, updating, coding, and packaging Microsoft Access 2016 Databases. I have been an Access user for about 16 years (give or take), and as recently as Access 2013 I've had corrupted databases or corrupted database objects (Forms mostly), with little explanation. Those situations (even with a backup) take a lot of time, making things like a memory upgrade a no-brainer, if that would indeed help stabilize. I switched to a Dell Precision a few months ago, with ECC RAM, and so far no corrupted forms, and our databases actually seem to run better. But I realize that may be due to other factors.
So in summary - would ECC RAM help improve Access 2016's performance (from a developer's) perspective. Any info would be great.
Thanks.
So in summary - would ECC RAM help improve Access 2016's performance (from a developer's) perspective. Any info would be great.
Thanks.
Dave Baldwin
You can't just install ECC RAM. The use of ECC RAM must be supported by the motherboard of the computer. Access knows nothing about the kind of RAM that is used in the computer. While some utility software can read the RAM specs, most 'normal' software knows nothing about it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Dave - thanks for input. I'm aware of that. Not talking about installing RAM on a system - but as a purchasing option decision.
ASKER
Carlo - thank you for the input. The question is not related to performance, but rather memory data errors that can cause Access or its objects to become corrupt. RAM and cache plays a role, but I don't know how much of one.
While a server machine that supported ECC RAM should be 'better', you don't yet have an actual correlation between the errors and any cause. In particular, there is no correlation between Access and ECC RAM. Access has no awareness of the kind of RAM being used.
ASKER
Thanks, Dave. You're probably right. But I'm seeing DB servers using it a lot more, likely for governance reasons. I think the key component is how Access uses memory when it's working with forms, maybe server/Sharepoint tables, and compacting, etc. you would think hat those processes are prone to crashes due to memory errors. I will leave this topic open a while longer just to see some more comments. Thanks again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks all for the help. This seems to be a situation of possibly buying insurance for possible crashes at a general, although possibly unlikely probability. However, given this system (workstation) is used to develop, test, and deploy an enterprise app, we'll likely go for the investment.