When we are registering the SQL component in Monitor 2023, Step 11 and 12 are bit confusing. What is the account crednetials that they are asking for in Step12 according to the document steps? Are they talking about the account that has read view permissions within the SQL environment where the DB that we are trying to configure lives? @DerekLaw
thanks
https://doc.arcgis.com/en/monitor/latest/get-started/windows/register-sql-server-databases.htm
Solved! Go to Solution.
Hi @Anonymous User,
> When we are registering the SQL component in Monitor 2023, Step 11 and 12 ... Are they talking about the account that has read view permissions within the SQL environment where the DB that we are trying to configure lives?
Step 11 refers to the database name. Step 12 - This is the account that you would use to login to the database, so ArcGIS Monitor can register and access its contents - to monitor.
Hope this helps,
Hi @Anonymous User,
> When we are registering the SQL component in Monitor 2023, Step 11 and 12 ... Are they talking about the account that has read view permissions within the SQL environment where the DB that we are trying to configure lives?
Step 11 refers to the database name. Step 12 - This is the account that you would use to login to the database, so ArcGIS Monitor can register and access its contents - to monitor.
Hope this helps,
@DerekLaw I'm also a bit stumped on registering a SQL server with my 2023 Monitor. Here I have my database shown in SSMS with my deployment wide ArcGIS Admin account logged in:
But I can't seem to get Monitor to recognize the user
I've tried without the domain in front of the user name, I've tried a couple other user names but nothing seems to work. Am I missing something about the login user?
Hi @ZachBodenner,
Have you confirmed that all the prerequisites to register a SQL Server database/geodatabase with Monitor have been met?
Hope this helps,
I had been sure, but I reviewed the prerequisites and I had been tripped up with this one:
I was attempting to use our deployment-wide admin account, which was a windows user that hadn't been given an explicit SQL login. So I got it working now, thank you!
edit: @DerekLaw so I should say, I got the database connected and I'm trying to set up the monitoring charts in this blog, but the gdb metrics(gdb_version, gdb_connections, etc) are not coming through as options when I try to set up the expressions:
Hi @ZachBodenner,
I've glad to hear you were able to register the database.
> ... the gdb metrics (gdb_version, gdb_connections, etc) are not coming through as options when I try to set up the expressions
I don't mean to state the obvious, but are you sure you registered an enterprise geodatabase (that is implemented on SQL Server) and not just a "regular" SQL Server database?
The gdb_ metrics are only available for enterprise geodatabase components and not "regular" databases.
Does the new different account that you used to register the database component with Monitor, does it have the correct access permissions to view the enterprise geodatabase?
Hope this helps,
I believe yes to both? If I check out the properties in Pro, it says it's an enterprise database:
and the user has all of the view permissions checked on (although not being a SQL pro, I could definitely be missing something here)
Hi @ZachBodenner,
Does the SQL Server account that you're connecting to the enterprise geodatabase with, have the following:
"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."
This is in the help topic I referenced in my previous post.
Hope this helps,