Modeling Configuration Items for SQL Server AlwaysOn or SQL Server Clustering from instance to database

[Jimmy Lin]

Hey guys, we are utilizing a lot of SQL Server Clustering and SQL Server AlwaysOn in our environment.  My question is how should this be modeled within ServiceNow CI and is there a way to do the discovery automatically.

With traditional clustering you have two physical nodes with 1 database instance and multiple databases

With AlwaysOn, you have multiple database instances (on single or multiple physical windows boxes), with AlwaysOn connected at the database level instead.

I was curious to see how to map this paradigm.  The goal is actually to map from application to database to some form of logical database instancing.

Thank you

[Henrik Jutterst]

I have done this.

Have you tried to run discovery on the database cluster and see what you get?

The issue I'm facing is that the database (catalogs) get the name of the active node instead of cluster name. For example:

<instance-name>@<server-name> instead of <instance-name>@<cluster-name>. I'm trying to solve this here (Wrong name for database instance in cluster!) but no lock so far.

[rohanlimaye]

Hi Any luck on this. I am facing similar issue where the automated service mapping is bringing wrong database name.