Increase or remove username field character limit in Enterprise Geodatabases

[DavidMcDermott1]

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. 

[JC_LAURENCE]

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 😞

[BillFox]

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-geodata...

[CarlTurner1]

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.

[CarlTurner1]

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.

[ShawnyEkadis]

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.