nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SQL Server required privileges to capture Geodatabase Metrics

B_Franey

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.

Find more posts tagged with

Accepted answers

StevenB1

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.

All comments

StevenB1

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.

B_Franey

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?

StevenB1

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

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.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.