This page provides information on how to determine checksums for objects imported using the Universal Importer. It can be useful to assist you in understanding why objects may be listed as modified in your analysis.
For more information, refer to:
- For CAST 7.3: Universal Importer
- For CAST 8.0: Appendix - Importing an additional technology not supported by CAST
- For CAST 8.3 Appendix - Importing an additional technology not supported by CAST AIP
|Microsoft SQL Server|
Checksums for Universal Imported objects come from the Universal Importer files for the technology being imported, just like the specific objects themselves. The checksums are imported from these files into the CAST databases. If the checksum value listed in the file changes between two versions of CAST, then the object will be shown as modified in CAST.
For example, if this is in the*.uax file which is being imported in the first version:
<instance id="S:\Sources\report1.wid" instanceOf="Report"> <identification name="report1.wid" fullName="S:\Sources\report1.wid"/> <checksum CodeAndCommentsChecksum="6d14e6fbf7ebce1ff6e67d4bc4fd5341" CodeOnlyChecksum="6d14e6fbf7ebce1ff6e67d4bc4fd5341"/> </instance>
The checksum for the report1.wid object that will be imported into CAST in the first version is 6d14e6fbf7ebce1ff6e67d4bc4fd5341.
If the *.uax file in the second version shows:
<instance id="S:\Sources\report1.wid" instanceOf="Report"> <identification name="report1.wid" fullName="S:\Sources\report1.wid"/> <checksum CodeAndCommentsChecksum="23caa4d9956c99740a13f95a7d03b819" CodeOnlyChecksum="23caa4d9956c99740a13f95a7d03b819"/> </instance>
The checksum for the report1.wid object that will be imported into CAST in the second version is 23caa4d9956c99740a13f95a7d03b819, which is different from the first version so that the object will appear as modified in the analysis.
The reasons for this change in checksum would need to be checked with the person who developed the custom Universal Importer technology that is being used and understands the process of how these checksums are assigned when creating the custom *.uax files that will be imported using the Universal Importer.
You can also see the checksum value in the database itself by querying the dss_object_info table. For example, a query like this:
select * from dss_object_info where object_id in (select object_id from dss_objects where object_name = 'report1.wid');
would result in the following data like the following:
which would show that in snapshot 1 the object_id 4660518 (which corresponds to report1.wid due to the query above) has a checksum of 23 while in the snapshot 2 the object_id 4660518 now has a checksum of 6. Since the checksum has changed, the object will show as modified in the analysis.