So calculating geometry (area) on a 10.8.0.25 SQL 2014 Enterprise Feature Class, Geography Storage Type, GCS projection in 2.5, not registered as versioned, no branch versioning, archiving enabled returns
ERROR 130051: Input feature class is not registered as versioned.
Failed to execute (CalculateGeometryAttributes)
Drew Flater I recall this coming up in the past, can't find the GN post though, or maybe it was in EAP. Is there now a requirement that feature classes have to be registered as versioned to calculate geometry?
SQL trace shows
Violation of UNIQUE KEY constraint 'states_cuk'. Cannot insert duplicate key in object 'dbo.SDE_states'. The duplicate key value is (0, 0). as this is happening.
Whats the version of SQL Server Enterprise?
Pro 2.5 has only been certified with SS 2014 and above.
I only ask to be sure because the associated version of management studio you listed seems to be from the SS 2012 time.
I see what you are asking.
I have limited access to some of this information. So there's back and forth on my end.
It's SQL Server 2012 and 10.3.1 on arcgis for server.
I'm not sure I'm saying that correctly, but I do understand what you are asking and I hope what I have written makes enough sense that you understand the server environment. But, if calculate geometry doesn't work on 2014 either... what version does it work on? (I ask bc I believe our IT department is getting ready to upgrade, so I would like to know what to tell them we need now and going forward).
Thank you for all of your help guys!
Happy Valentine's Day to you <3
I looked online at the specs. Supported OS = Windows Server 2012 R2 Standard and Datacenter.
Also, on this webpage https://pro.arcgis.com/en/pro-app/get-started/arcgis-pro-system-requirements.htm there's a link to check your computer's ability to run ArcGIS Pro 2.5.
I took an interest in your question because i work with versioned and non versioned ediitng as part of the development work here. Like Drew with Thomas' question, I couldn't reproduce your problem with Pro 2.5 and SQL Server 2014 but we also run with relatively clean non production databases.
I would probably work with support on this issue unless somebody else chimes in soon. If you do contact support they will likely ask you to upgrade sql server. Upgrading may not solve the issue right away but at least we know it should work.
The list of currently supported versions can be found at: Microsoft SQL Server database requirements for ArcGIS 10.8 and ArcGIS Pro 2.5