MS SQL Database instance_name not always set

Patrick Oudsho1
Tera Contributor

Hi all,

 

We noticed that during the discovery and creation of our MS SQL Databases the instance_name (link to MS SQL Instance) is not always set.

 

I tried to figure out where setting this value was done, so I could investigate why it is not always working and being set, but wherever I look (Pre/Post Pattern scripts, Business Rules, Script Includes) nowhere it seems this is set.
Checking the results in the ECC Queue, the instance_name is also not set during pattern executing on the MID-server.

 

Does anyone have a clue where the cmdb_ci_db_mssql_database.instance_name is set during discovery so I can investigate why for some discovered DBs this is not set?!?

1 ACCEPTED SOLUTION

Rahul Priyadars
Giga Sage
Giga Sage

Hi Patrick

 

Please have a look at this App Pattern- MS Sql DB On Windows

 

RahulPriyadars_0-1702614265960.png

did u tried running in debug mode.

Regards

RP

View solution in original post

4 REPLIES 4

Rahul Priyadars
Giga Sage
Giga Sage

Hi Patrick

 

Please have a look at this App Pattern- MS Sql DB On Windows

 

RahulPriyadars_0-1702614265960.png

did u tried running in debug mode.

Regards

RP

Hi Rahul,

 

Thanks, I thought I had checked it all, but in the library 'MSSQL populate database table ' used by the MS Sql DB On Windows pattern in its last step it created the relationship indeed.

Schermafbeelding 2023-12-15 084611.png

+1 ..Good to see you found that.

Regards

RP

where can this be found?