Limitation using RAT Plugin for Integrity with MS ACCESS database
7 years 2 months ago - 7 years 2 months ago #90
by javier-fernandez
Limitation using RAT Plugin for Integrity with MS ACCESS database was created by javier-fernandez
Hi everybody!
This is a report from our Integrity expert about a known problem due to the technology beside the RAT Plugin for Integrity that conflicts with the technology of MS ACCESS.
The PTC Integrity extension mechanism used to launch the RAT Plugin for Integrity consists on configuring a Custom Tool. This method run the executable given in the Custom Tool configuration.
Due to the time-consuming while opening the RAT Plugin for Integrity, it will stay resident as a tray application after the first time. This means that the following tasks will be way faster.
This approach resides in a technology called Windows Communication Foundation (WCF), which is a multithread process. It is well known in the community that the multithread feature causes problems when using MS ACCESS database. The technical reason behind that is that the MS ACCESS doesn't work as a service process but as a libraries loaded in the thread that establish the connection to the database individually.
The expected behaviour is that the RAT Plugin for Integrity will randomly crash when performing some database operations, especially when saving requirements using the RAT Plugin for Integrity. This kind of random crashes do not cause where using the other types of databases like MS SQLServer or MySQL.
Having said that, we recommend having SQLServer or MySQL as the Ontology database, instead of MS ACCESS.
Cheers!
This is a report from our Integrity expert about a known problem due to the technology beside the RAT Plugin for Integrity that conflicts with the technology of MS ACCESS.
The PTC Integrity extension mechanism used to launch the RAT Plugin for Integrity consists on configuring a Custom Tool. This method run the executable given in the Custom Tool configuration.
Due to the time-consuming while opening the RAT Plugin for Integrity, it will stay resident as a tray application after the first time. This means that the following tasks will be way faster.
This approach resides in a technology called Windows Communication Foundation (WCF), which is a multithread process. It is well known in the community that the multithread feature causes problems when using MS ACCESS database. The technical reason behind that is that the MS ACCESS doesn't work as a service process but as a libraries loaded in the thread that establish the connection to the database individually.
The expected behaviour is that the RAT Plugin for Integrity will randomly crash when performing some database operations, especially when saving requirements using the RAT Plugin for Integrity. This kind of random crashes do not cause where using the other types of databases like MS SQLServer or MySQL.
Having said that, we recommend having SQLServer or MySQL as the Ontology database, instead of MS ACCESS.
Cheers!
Please Log in or Create an account to join the conversation.
