this post was submitted on 28 May 2025
13 points (93.3% liked)

Sysadmin

10020 readers
85 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world

founded 2 years ago
MODERATORS
DarraignTheSane@lemmy.world
00Lemming@lemmy.world
L3s@lemmy.world
13
Do you separate your asset database and CMDB? (lemmy.world)
submitted 1 month ago by charlotte_starhive@lemmy.world to c/sysadmin@lemmy.world
5 comments fedilink hide all child comments
 

Hi, I can't seem to find if there's a consensus on this so asking here.

Not all CIs are assets and not all assets are CIs. But many assets and CIs are the same physical or virtual thing.

I see some vendors (e.g. ServiceNow, Freshservice) have separate asset databases and CMDBs. and other (e.g. Jira Service Management) have a combined database.

Do you have any preference one way or the other? Are there pros and cons to do it a certain way? To me it seems like maintaining two databases is more fiddly and time consuming but I don't know.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Unforeseen@sh.itjust.works 3 points 1 month ago (1 children)

Typically I've found it better to be combined both for process integration and ease of administration like you said.

It can make sense to separate it but it totally depends on the company.

I also think it's always easier to start with everything in the cmdb and separate things later if it makes sense to do so vs the other way around.

[โ€“] charlotte_starhive@lemmy.world 1 points 3 weeks ago

Thanks for sharing. And agree, never thought about needing to separate them out later but definitely easier to split rather than combine