The Results database is a data warehouse containing all results data for CM4D. It is an extension to the CM4D databases but is not managed directly by the CM4D Site database. For end-users of CM4D, however, the Results Database and CM4D Databases are all a single storage entity.
CM4D is designed to pass messages/data to the Results database. If a Results database is enabled but not configured properly or available, CM4D will detect this and treat it as an error condition.
If you do not want to use the Results database, simply disable the Results Datasource in Site Manager and do not complete any configuration for the results-related parts of the system (results database, results services, results rules, etc.).
Without the Results database configured you will miss out on the benefits of having a high-performance repository of information available for business analysis. In future versions of the product, the Results data will become a key part of the development path.
No. The CM4D databases are required, as they operate in tandem with the Results database, for some of the following reasons.
DataSmith loads, verifies and manipulates data files.
CM4D does the evaluation and analysis that feeds results.
CM4D has raw data for re-evaluation, if things change.
The Actual measurements and Nominals are loaded in the CM4D database.
CM4D calculates alignments, constructions, pattern matching, 3D transformations, etc.
CM4D relates all measurements directly to CAD to in 3D space.
Complex reports cannot be reproduced in dashboards.
BI Tools are to slow when calculating complex statistics (e.g., Cp/Cpk).
Automatic alarming and e-mailing is more structured.
For most users, the databases will always synchronize automatically. The only instances where the two database types may get out of sync are following an upgrade from a version of CM4D that never had a Results database, if you delete the Results database for some reason and need to create a new one, or some other case where something interferes with the communication between the two databases (e.g., deleted queues/messages). In the rare case where the databases need to be brought back into alignment, there are tools built in to CM4D to assist with the synchronization process.
Can we improve this topic?