POST
|
Direct updates to the spatial column of geodatabase data are supported, but only under specific workflows, and there are still caveats. Are you writing in a shape defined as a CIRCULARSTRING or CURVEPOLYGON? ArcGIS only supports simple, densified line geometries (LINESTRING, POLYGON etc). Circular arcs are stored in the gdb_geomattr_data column, and their densified versions are stored in the shape field. If there is a circular arc version of a shape, ArcMap or ArcGIS Pro will read it, but it will not read circular arcs from the Shape field.
... View more
01-24-2023
11:45 AM
|
0
|
1
|
254
|
POST
|
did you get an error executing the grant statement in Management Studio, or did you get a specific error when the user tried to access the data on the schema you granted to?
... View more
01-24-2023
11:37 AM
|
0
|
3
|
834
|
POST
|
ArcGIS Enterprise 11.0 and Pro 3.0 already contain the ODBC fix so need no further patching to work with SQL Server 2022.
... View more
01-23-2023
04:15 PM
|
0
|
0
|
2526
|
POST
|
Our support for 2022 isn't tied to database compatibility level. We have not completed certification testing for 10.9.1 / Pro 2.9.x on SQL Server 2022 but should do so shortly. Connections to SQL Server 2022 will need to be made using the ODBC Driver 18. Supporting this driver required a software change which was made with BUG-000147765. This bug was fixed in 10.9.1 Utility Network and Data Management Patch 2 as well as ArcGIS Pro 2.9.4. Once our certification is complete, working with SQL Server 2022 will require installing those patches/releases.
... View more
01-23-2023
04:14 PM
|
0
|
3
|
2531
|
POST
|
Could it be that the database was overwritten with an older backup? Could you check with whomever manages the SQL Server instance to see if you can get the upgraded database back? There isn't any straightforward, or supported way to get anything out of a really old ArcSDE database without ArcGIS software. The data pre-dates SQL Server spatial types, which wasn't introduced until 2008, so all the spatial data would still be in sdebinary format. The 'geodatabase' component was in the old model where any behavior (subtypes, domains, relationships etc) was stored in blob formats. Before trying to hack anything at the database level I'd exhaust the possibilities of getting a newer backup restored, or getting access to old ArcSDE software to perform the upgrade.
... View more
01-18-2023
04:22 PM
|
1
|
7
|
616
|
POST
|
It is likely that the geodatabase you can connect to has been upgraded to a 10.x release. Geodatabase upgrades are separate from upgrading ArcMap and ArcGIS Pro, as well as SQL Server. Are you able to connect directly to the SQL Server instance using SQL Server Management Studio? If you can, look for a table called sde_version and compare the contents between the database you can connect to, and the one you to which you cannot. Newer ArcGIS clients cannot upgrade geodatabases that are at versions earlier than 10.1. Major changes were made to the structure of geodatabases at 10.0, and upgrades to 10.0 or later releases could only be done from a geodatabase that was upgraded to 9.3. Do you have access to older versions of ArcSDE software? This is going to be the only way to get the 9.1 database upgraded to a point where it can either be seen from 10.x and Pro software, or upgraded to something that can be connected to. This doc from 10.1 https://resources.arcgis.com/en/help/main/10.1/index.html#/A_quick_tour_of_enterprise_geodatabase_upgrades/002q0000005p000000/ outlines You can upgrade ArcSDE 9.3, 9.3.1, or 10 geodatabases to geodatabase release 10.1. If your geodatabase is at a lower release, you must first upgrade to a supported release, then upgrade to 10.1. Getting to 9.3 from 9.1 is going to require ArcSDE software - upgrades prior to 10.x were done using ArcSDE software, not Desktop applications like ArcMap. -Shannon
... View more
01-18-2023
01:53 PM
|
1
|
10
|
1016
|
POST
|
ArcGIS Pro 3.0 and ArcGIS Enterprise 11, as well as upcoming 3.1 and 11.1 releases are supported with SQL Server 2022. The system requirements documentation will be updated to reflect this shortly.
... View more
01-13-2023
01:11 PM
|
3
|
5
|
2577
|
IDEA
|
This post covers renaming a SQL Server database in more detail: https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/restoring-sql-server-databases-with-a-new-name/
... View more
06-29-2022
10:23 AM
|
0
|
0
|
2503
|
IDEA
|
Support for PostgreSQL 12 was added with ArcGIS 10.8.1 and ArcGIS Pro 2.6 https://desktop.arcgis.com/en/system-requirements/latest/database-requirements-postgresql.htm
... View more
11-19-2020
03:14 PM
|
0
|
0
|
627
|
POST
|
Michael, unfortunately connections to SQL Server Data Warehouse, Azure SQL Data Warehouse, or Azure Synapse are not currently supported from ArcGIS clients. However, in building a road map for data sources we may support in the future we are interested in more information about your workflow, the type of data you are storing there, and how you want to interact with it. Thanks, Shannon
... View more
09-08-2020
06:51 PM
|
3
|
1
|
4824
|
POST
|
Hi Erik, I was just forwarded your post - sorry that no one responded earlier. This Microsoft documentation can shed a little light on your issue: sys.dm_db_objects_disabled_on_compatibility_level_change (Transact-SQL) | Microsoft Docs It is nothing to really be concerned with - there were some functional changes to spatial type methods between 2008 and 2012 (or any later release) that 'invalidated' certain objects like check constraints. The check contraints in your database are placed automatically on the spatial column of any feature classes created by ArcGIS software. They are there to prevent shapes with invalid SRID values from being inserted into the column. If you ever insert or update shapes outside of ArcGIS software (e.g. at the SQL level or a 3rd party application) then you will want to change these contraints back to 'CHECK' from NOCHECK. If you don't then they can be left as-is. -Shannon
... View more
09-08-2017
02:02 PM
|
0
|
0
|
550
|
POST
|
This will be fine on SQL Server - by default all logfiles, keyset tables & other temporary objects are created in tempdb. No additional permissions are required for this.
... View more
04-24-2017
02:34 PM
|
1
|
0
|
1130
|
POST
|
Do you know which updates were installed? Were these OS updates? SQL Server updates? What version of SQL Server are you using?
... View more
01-20-2017
02:10 PM
|
0
|
0
|
318
|
POST
|
There is a Knowledge Base article that describes this issue in detail: http://support.esri.com/technical-article/000014556 -Shannon
... View more
01-03-2017
04:32 PM
|
1
|
0
|
645
|
IDEA
|
SQL Server Management Studio absolutely does drop your table and create a new one. Run a Profiler or XEvents trace to see the SQL that is being issued - you'll see the creation of a new table, copying of the data, dropping of the original table, renaming of the new table. This is why you have to disable the 'Prevent saving changes that require table re-creation' Table option. If you do not disable this option, you will not be able to save changes like reordering columns. SQL Server doc: Change Column Order in a Table There is no magic ALTER TABLE statement for reordering fields. Changing the physical order of columns will require re-ordering everything physically at the page level. This is not a trivial operation and I'll venture a guess that this is why none of the commercial dbms that we support do this - it is probably safer/cleaner to recreate the entire table.
... View more
07-08-2016
11:23 AM
|
3
|
1
|
856
|
Title | Kudos | Posted |
---|---|---|
1 | 2 weeks ago | |
1 | 3 weeks ago | |
1 | 3 weeks ago | |
4 | 05-01-2023 11:02 AM | |
1 | 03-17-2023 11:42 AM |
Online Status |
Offline
|
Date Last Visited |
Friday
|