Latest Contributions by ShannonShields

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

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

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

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

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

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

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

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

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

Do you know which updates were installed? Were these OS updates? SQL Server updates? What version of SQL Server are you using? ... View more

There is a Knowledge Base article that describes this issue in detail: http://support.esri.com/technical-article/000014556 -Shannon ... View more

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

Re-ordering the fields using the Table View (right-click on the layer, click Design, and Fields) will allow you to save the order in your project. You must save the changes that you make in the Field View for them to stick. This isn't physically re-ordering them in the underlying dbms table, but changing the order in which they are queried when you open the attributes of the layer in your map. This is a little different than ArcMap, but the equivalent functionality is there. ... View more