topic Re: Utility network priviledges in ArcGIS Utility Network Questions

Utility network priviledges

FilipKuzman — Wed, 22 Apr 2020 11:18:36 GMT

Hi everybody,

I am trying to grant privileges in my Enterprise Geodatabase for the Utility Network dataset to the other users in SQL Server. Dataset is branch versioned. I have added users through the GP tool Create Database User in ArcGIS Pro and then assigned dbcreator role to them in SQL Manager. However, if I try to add privileges to any of them on my UN dataset(as UN owner) I got 'Unsupported operation for utility network datasets.' Even just for select option. Does the UN support multi-users on its dataset? Or am I missing something?

Thank you

Re: Utility network priviledges

AnthonyRyanEQL — Wed, 22 Apr 2020 12:42:53 GMT

Filip,

I'm working on a Utility Network project and we have created a read only user within SQL Server 2016 to access the schema that the utility network resides in.

This was development by our implementation partner

SQL to execute

USE [<db_name>]
CREATE USER [<RO username>] FOR LOGIN [<RO username>] WITH DEFAULT_SCHEMA=[<UN schema name>]
GRANT SELECT ON SCHEMA :: [<UN schema name>] TO [<RO username>]

Good luck

Re: Utility network priviledges

FilipKuzman — Wed, 22 Apr 2020 12:57:39 GMT

That worked!

Thank you Anthony.

Re: Utility network priviledges

PierreloupDucroix — Mon, 09 Feb 2026 04:06:54 GMT

Hello, does anyone have more information on this?

Is this normal behavior in Utility Network? If so, why?

I've reproduced the problem with ArcGIS Pro 11.5 and PostgreSQL.

I was able to grant read access to a UN dataset via SQL, but not through ArcGIS Pro's privilege management.

Re: Utility network priviledges

RobertKrisher — Mon, 09 Feb 2026 14:16:58 GMT

Users should not be directly connecting to the geodatabase to access utility network data, they should be using services.

Re: Utility network priviledges

PierreloupDucroix — Mon, 09 Feb 2026 21:00:19 GMT

Thanks, Robert. We primarily use the SDE connection file to export data from the default version via administrative toolboxes or scheduled tasks.

I know feature services and the Portal offer better privilege management, but in some cases, direct access to the geodatabase offers better performance than using a feature service, and I don't want to share the data owner's connection file. That's why a read-only user would be helpful.