Database CI to Application Service Relationships
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 03:50 AM
Hi guys,
I am after a little advice around mapping database CIs to application services. We recently mapped 120 SQL servers (windows servers) to application services during one of our first iterations of creating a meaningful CMDB.
These windows servers have MSFT SQL instances that run on them. The instances then contain MS SQL databases. This means that I can follow a downstream path from our application service to the MS SQL databases that underpin it.
However, not all databases contained in that particular instance (that runs on that particular windows server) relate to that particular application service.
Ideally, we would want to show precisely which databases make up an application service. The only issue is, we have 5000+ SQL databases. Maintaining such relationships would be impossible if approached manually.
Does anyone have any suggestions around how SQL databases can be mapped to their respective application services? Can top-down discovery be leveraged for this? Or, is this even the right approach in the first place?
The way I see it, we could have related 1 of 3 things to the application service when conducting our first phase of manual service mapping- the server, the instance, or the database. What relationships are suggested?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 11:59 AM - edited 08-02-2023 12:00 PM
It has been a while since I did any Service Mapping development, but I believe the database would be what gets related there. The instance and server are not.
