My experience is that nothing happens to the asset when the associated CI is archived. In fact, you can still open the asset and see the CI reference. If you open the CI reference, you see that the CI is now in the archive table. You can find the assets which have had their CI's archived by setting the following filter conditions on the asset table:
"Configuration Item" is not empty
-and-
"Configuration.Sys ID" is empty.
I'm trying to figure out what is best practice regarding this issue. I've seen some discussions saying not to archive CI's with associated assets. But that becomes problematic when the CMDB grows extremely large.
I'm thinking of adding a custom "needs archiving" flag to both the ci table, and the asset table, and setting up a business rule on the CI table which sets the "needs archiving" flag based on the criteria I am currently using in my archive rule. But my business rule would also check for an associated asset and also set the asset's "needs archiving" flag. Then I would create archive rules for both CI's and Assets which is checking for the "needs archiving" flag.
