Linking cmdb_ci_server and cmdb_ci_spkg

miyu
Tera Guru

The following document stated to use the "cmdb_sw_instance" table to link Hardware and Software, but I could not find the "cmdb_sw_instance" table in the table list.
Which table are you referring to?

https://docs.servicenow.com/ja-JP/bundle/rome-servicenow-platform/page/product/configuration-managem...

1 ACCEPTED SOLUTION

CMDB Whisperer
Mega Sage
Mega Sage

I cannot read the article because it is in Japanese, but I can tell you that the table name you specified is incorrect.  The correct table name is cmdb_software_instance not cmdb_sw_instance.  It is installed on all instances out of the box, so you are probably just using the wrong table name in your search.  You do not need Discovery or SCCM or any other plugins to enable this table.  That said, it sounds like you are looking to manually associate your servers with the software that is installed on them, and typically/preferably this is populated by a source such as Discovery or SCCM rather than populating it manually.  If you are not licensed for Discovery I would suggest contacting your Server management team(s) and asking what they use managing their server configurations and deploying software.  You may be able to integrate that application into ServiceNow and automatically populate your software installations.


The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

View solution in original post

4 REPLIES 4

Community Alums
Not applicable

Hi @miyu ,

You need to make sure you have all the related Plugins are installed for Discovery, SCCM,etc..

 cmdb_sw_instance table is the table where all the installed instances of the SW packages are installed and I presume that this table obtains this info from SCCM.

The cmdb_ci_spkg table is more a roll-up of the cmdb_sw_instance table so it contains the SW packages (that in this case are 'discovered' by SCCM) and the versions and total count per package per version.

When this is indeed the case than I should suggest to check the cmdb_sw_instance table and make corrections over there as this will/should result in corrections on the spkg table.

Hi @Community Alums .

Thank you, what is SCCM?

CMDB Whisperer
Mega Sage
Mega Sage

I cannot read the article because it is in Japanese, but I can tell you that the table name you specified is incorrect.  The correct table name is cmdb_software_instance not cmdb_sw_instance.  It is installed on all instances out of the box, so you are probably just using the wrong table name in your search.  You do not need Discovery or SCCM or any other plugins to enable this table.  That said, it sounds like you are looking to manually associate your servers with the software that is installed on them, and typically/preferably this is populated by a source such as Discovery or SCCM rather than populating it manually.  If you are not licensed for Discovery I would suggest contacting your Server management team(s) and asking what they use managing their server configurations and deploying software.  You may be able to integrate that application into ServiceNow and automatically populate your software installations.


The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.