SAM (Software Asset Management) Tables and Data Migration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2024 12:58 AM
Hello Team,
appears it is surprisingly difficult to find reliable information about how SAM changes some of the related tables and data, so I hope someone can help!
I need to know in detail what changes in the functionality and interactions between below three tables after SAM Pro is installed.
Software Package (cmdb_ci_spkg), Software Instance (Installed On) (cmdb_software_instance), Software Installs (cmdb_sam_sw_install), and Discovery Model (cmdb_sam_sw_discovery_model).
- What is the purpose of each of those tables?
- Which records are migrated from where to where?
- Do they remain as a reference in the initial table after migration?
- If they remain, are they further being updated?
- What are the jobs/ BRs driving this behavior?
- Do the previous relationships between those tables and other tables still exist or manual adjustment is needed?
- How do we ensure CMDB related processes around SW remain functional after installation of SAM Pro?
- How do we ensure the correct import & mapping of SW data when we import from an instance without SAM Pro installed to an instance with SAM Pro?
I hope you can help!
Many thanks!
Best regards,
Rado
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 02:44 AM
Hello, Rado.
Have you had the chance to see the answer for this?