AnsweredAssumed Answered

ArcGIS 10.5.1 & ArcGIS Pro 2 bug connecting to sql server ?

Question asked by albertoaloe on Jul 14, 2017
Latest reply on Jun 19, 2018 by use2b311

Hi guys.

I'm experiencing something weird when connecting  a fresh ArcGIS 10.5.1 installation to a geodatabase in sql server. Basically, the  geodatabase does not retain previously set privileges on database objects according to the following scenario:


A user (data viewer or data creator with his own schema), able to access geodb objects owned by other users from ArcGIS 10.4/ ArcGIS 10.5, cannot access them any more despite permissions at sql server level are ok (the user can access them through SSMS).


A user with SELECT privilege at schema level (let's say for dbo) cannot view item in ArcGIS 10.5.1 that were previously consumed from ArcGIS 10.4/ ArcGIS 10.5


Further details as follows:

  • It does not apply to dbo
  • Enforcing SELECT privilege at ArcGIS level (in ArcCatalog) works fine and makes the object available to the user
  • This behavior does not depend on geodatabase schema version but only on ArcGIS client version (10.5.1)
  • ArcGIS Pro 2 behaves the same way while ArcGIS Pro 1.4 was working fine


I'm using ArcGIS 10.5.1 /ArcGIS Pro 2 against sql  server 2014