idea Increase or remove username field character limit in Enterprise Geodatabases in ArcGIS Pro Ideas

Length of long identifiers in enterprise databases

ajelenGDi — Fri, 24 Sep 2021 15:22:52 GMT

Our organization is using Oracle 12c/19c enterprise databases. When we create new field name with more then 30 characters, ArcGIS (ArcMap or ArcGIS Pro) truncates name to 30 characters. With Oracle 12.2 version was increased the maximum size of most identifiers from 30 to 128 bytes. It will be useful to implement this functionality also in ArcGIS Pro. Some use cases: end user has field name consisted of organization name, department name, project name, attribute name etc. ArcGIS does not allow 43 characters, it truncates to 30 characters. Check attachments.

Here is Oracle article about this functionality: https://oracle-base.com/articles/12c/long-identifiers-12cr2
We are aware that this is not a bug but enhancement what we are asking for.

Re: Lenght of long identifiers in enterprise databases

KoryKramer — Fri, 24 Sep 2021 15:21:31 GMT

If you look at https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEwNjY0Mw== the Alternate Solution indicates that using the Add Field tool should allow you to create a field with a name longer than 30 characters.

This idea is related to the following open Enhancement Request [ENH-000108054: ArcGIS should allow more than 32 characters as the length of column names in supported DBMSs that allows this functionality.]

Re: Length of long identifiers in enterprise databases

ajelenGDi — Mon, 27 Sep 2021 12:12:10 GMT

@KoryKramerHi. I tried you alternative solution but it does not work. ArcGIS Pro truncates 60 characters long field name to 30. Please check printscreen.

Re: Length of long identifiers in enterprise databases

KoryKramer — Mon, 27 Sep 2021 12:36:29 GMT

Oops - must still not work with Oracle. I was just able to add a 64-character named field to a file geodatabase using the geoprocessing tool. As stated above, the idea is associated with ENH-000108054.

Increase or remove username field character limit in Enterprise Geodatabases

DavidMcDermott1 — Thu, 24 Jul 2025 20:07:35 GMT

When creating a database connection for PostgreSQL, the username field has a limit of 30 characters. This is particularly frustrating when trying to connect to PostgreSQL on Azure as the username format needs to be ‘user@host’. This limit needs to be increased or removed.

Re: Increase or remove username field character limit for PostgreSQL

TimMollison_infra — Thu, 25 Aug 2022 02:11:24 GMT

A similar constraint applies to the username for SQLServer connections using Azure Active Directory (available in ArcGIS Pro v3.0.0) where "@domain" is part of the username. Our domain is over 20 chars and usernames are in the form firstname.lastname and so only people with short names like 'john.doe' are able to connect.

Re: Increase or remove username field character limit for PostgreSQL

BrianCunningham001 — Thu, 27 Oct 2022 16:04:29 GMT

Is there a workaround for this?

Re: Increase or remove username field character limit for PostgreSQL

CDischinger — Tue, 04 Mar 2025 17:18:23 GMT

Why are we still facing this issue?

Re: Increase or remove username field character limit for PostgreSQL

LisaZygo — Tue, 04 Mar 2025 17:20:52 GMT

Please help get this issue resolved as we're facing it with Azure SQL

Re: Increase or remove username field character limit for PostgreSQL

GerardoGarcia — Tue, 04 Mar 2025 18:44:09 GMT

I don't think this is just specific to PostgreSQL. It looks to be a limitation of Pro, which is disappointing to say the least. And this post has basically gone unanswered since 2021? A tool like SQL Server Management Studio works without this issue. Why is ESRI software still behind?

Re: Increase or remove username field character limit for PostgreSQL

PaulSanders — Tue, 04 Mar 2025 19:46:17 GMT

We need this character limit to be addressed. Causes a huge problem for organizations utilizing cloud platform databases like Azure SQL.

Re: Increase or remove username field character limit for PostgreSQL

JC_LAURENCE — Tue, 29 Apr 2025 16:02:28 GMT

We very much want to migrate our SQL Server (both 'regular' and managed instance) geodatabase logins over to Azure Entra ID authentication, but are being held back by this arbitrary maximum length. In addition, the ArcGIS Pro UI seems to apply the limitation to server logins rather than just to database users. I think there's a built-in assumption that a server login name and the mapped database user name are the same value, so we can't even shorten the database user names below the threshold while keeping the login names intact. The domain portion of our Entra ID UPNs is 26 characters long, so almost all of our UPNs exceed the ESRI maximum.
ESRI please address this soon, because it's a very big and very arbitrary limitation and we're still stuck using sql server authentication 😞

Re: Length of long identifiers in enterprise databases

BillFox — Mon, 12 May 2025 23:56:18 GMT

ENH-000108054 ArcGIS should allow more than 32 characters as the length of column names in
supported DBMSs that allows this functionality.

old, Field (column) name = 31

new for Pro 3.5 now shows: Field (column) name = 128 for SQL server

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/enterprise-geodatabase-limits.htm

Enterprise Geodatabase Username Character Limit

CarlTurner1 — Thu, 03 Jul 2025 17:24:09 GMT

When connecting to an enterprise geodatabase (AzureSQL) there has always been a 32 character limit for usernames. With the advent of EntraID integration, it is very easy to exceed this limit because it the character limit includes the '@mycompanydomain.com' of the username. This makes the EntraID options almost unusable for many organisations.

My idea is to remove this character limit or, at least, to ignore the domain component of a username in the count.

Re: Increase or remove username field character limit for PostgreSQL

CarlTurner1 — Thu, 03 Jul 2025 17:28:54 GMT

Agree with this. The character limit means that the EntraID integration options are virtually unusable for an organisation, like ours, with a long domain.

As above, we are limited to using SQL accounts, which is considered a security risk by our Cyber Security team.

Re: Increase or remove username field character limit for PostgreSQL

ShawnyEkadis — Wed, 09 Jul 2025 17:32:53 GMT

This is a also a problem for us as well. We also use single sign on with Entra so we've had to create a database login for a user because her account name is too long. This is not best practice for our department but it's the only way we could move forward. There is a bug enhancement scheduled for a future release, but no specific date was given: (https://my.esri.com/#/support/bugs/bugs?bugNumber=ENH-000121539)

Esri please make this a priority.

Re: Increase or remove username field character limit in Enterprise Geodatabases - Status changed to: In Product Plan

SSWoodward — Thu, 24 Jul 2025 20:07:44 GMT

Re: Increase or remove username field character limit in Enterprise Geodatabases - Status changed to: Implemented

SSWoodward — Tue, 25 Nov 2025 19:19:19 GMT

Thanks everyone for your contributions to this Idea.

In ArcGIS Pro 3.6, max user name lengths in Enterprise Geodatabases now mirror the max length supported by the RDBMS.

For more new features, check out the `What's new in ArcGIS Pro 3.6` release blog.

Re: Increase or remove username field character limit in Enterprise Geodatabases

Sarah_Hanson — Tue, 06 Jan 2026 17:58:29 GMT

The same is true for cloud data warehouses as well (Snowflake, Google BigQuery, and Amazon Redshift), beginning with the ArcGIS Pro 3.6. release. Relevant doc here.