What is the correct table to store relationships between Services, other Services and other non-Service CI's ?

[keviningleby]

Hi folks,

I quickly mocked up a CI-relationship/depedency map between different Services (with different Service Classifications) and other CI's such as Applications - using the "cmdb_rel_ci" table   and "Depends on:Used by", etc. (I also used the "Parent" facility between "Shared Service", "Technical Service" and "Business Service" and configured a "tree-picker" form to take advantage.

All worked fine.

Then I noticed this manual page -

Business service tables

- which suggests that I should have used the "svc_ci_assoc" table for this purpose.

Can anyone enlighten me as to why this should be so - and also perhaps explain the purpose of the "svc_rel_assoc" table (should I be populating this too) ?

Many thanks

Kevin

[keviningleby]

Thanks Jake.

Back in "my world does not include ServiceWatch right now" but I'm hoping to get around to it one day" ......

Are we safe to go with "cmdb_rel_ci" or should we be using "svc_ci_assoc"   ?

What is the SN "best practise" on this ?

Many thanks

Kevin

[snowtech1]

Currently, does anyone have more thoughts to this? We too don't have service mapping, and use only discovery.

[keviningleby · Accepted solution]

Indeed there is !

Great initial thoughts though guys.

Cheers !

Kevin