Select to view content in your preferred language

SQL Server required privileges to capture Geodatabase Metrics

341
4
Jump to solution
07-07-2025 01:03 PM
B_Franey
Occasional Contributor

What are the SQL Server required privileges to capture Geodatabase Metrics? We have registered an Enterprise Geodatabase that is getting DB metrics just not Geodatabase Metrics.

0 Kudos
1 Solution

Accepted Solutions
StevenBeothy
Regular Contributor

Hi ArcGIS Monitor's help states:

  • A SQL Server-authenticated user account must be used to register the database for monitoring and must be mapped to the database and be granted the View server state permission on the database instance. To monitor a geodatabase, the SQL Server user account's default schema must be the same schema in which the geodatabase system tables are stored.

I like to register the geodatabase with the sde administrator credentials so to collect all of the Geodatabase metrics in this link.

View solution in original post

4 Replies
StevenBeothy
Regular Contributor

Hi ArcGIS Monitor's help states:

  • A SQL Server-authenticated user account must be used to register the database for monitoring and must be mapped to the database and be granted the View server state permission on the database instance. To monitor a geodatabase, the SQL Server user account's default schema must be the same schema in which the geodatabase system tables are stored.

I like to register the geodatabase with the sde administrator credentials so to collect all of the Geodatabase metrics in this link.

B_Franey
Occasional Contributor

Our user has all of these requirements met and is still not getting geodatabase metrics.

A SQL Server-authenticated user account must be used to register the database for monitoring and must be mapped to the database and be granted the View server state permission on the database instance.

Who marks these as Solved?

0 Kudos
StevenBeothy
Regular Contributor

I believe Derek Law the forum moderator marked my answer as correct.
If you are following all of the above points another potential road block could be a firewall between the ArcGIS Monitor server and your SQL Server machine. Make sure all the prerequisites are met from this link.

  • The database instance must have the TCP/IP protocol enabled.
  • The firewall must allow communication between Monitor Agent and the SQL Server machine on port 1433.
    Note: If SQL Server is configured to run on a different port, communication must be allowed on that port instead.
DerekLaw
Esri Esteemed Contributor

Hi @B_Franey,

Who marks these as Solved?

Yes, it was me who marked it as solved. I thought @StevenBeothy's response was good and since you hadn't responded in over a month, I thought you were good. Apologies for the oversight on my part.

0 Kudos