Latest Contributions by TinaMorgan1

I'm sure there is a way.  In the world of technology there is always a way...but is it a tried and true tested way?  If you think this issue requires a fix outside of the tools Esri currently provides then we want to know about it in Support so we can either fix any workflow issues, or get this work case up to development to develop a tool that does what you need in the tried and true way. Your current support case should (most likely, never set in stone) take one of those two routes:  workflow correction, or bug logging. ... View more

All of the research I am doing on the particular error states that you would see this if using an older ArcGIS client.  If you double checked that you are using 10.5.1, then call Esri Support for further investigation.  My hunch is that there is a minor upgrade or setting that was missing, but without more insight I don't want to make any suggestions. ... View more

At ArcGIS 10.5, feature classes you create in a geodatabase in SQL Server that use Geometry or Geography storage will store attributes such as pointIDs, multipatches, and parametric entities (true curves) directly in the business table. Prior to ArcGIS 10.5, this information was stored in a side table that joined with the business table. Note that 10.3 and earlier clients cannot connect to feature classes that use this new type of storage. http://desktop.arcgis.com/en/arcmap/latest/get-started/introduction/whats-new-in-arcgis.htm I am assuming the feature are inaccessible from ArcCatalog in the preview tab, as well as all other ArcGIS applications...what version of ArcCatalog are you using to preview this data?   ... View more

This thread is a bit older, but wanted to add a tid bit from a case I just got.     If you happen to rename the database in SQL Server, and do not remember the original geodatabase name, you can check that in the database_name column of your sde_table_registry table.  That table hard codes the name of the database as it was when the geodatabase was created. Methods to move a geodatabase in SQL Server—Help | ArcGIS Desktop  ... View more

This thread is a bit older, but wanted to add a tid bit from a case I just got.   If you happen to rename the database in SQL Server, and do not remember the original geodatabase name, you can check that in the database_name column of your sde_table_registry table.  That table hard codes the name of the database as it was when the geodatabase was created. ... View more

Ensure that your attribute edits are not violating any constraints placed by domains, subtypes, relationship class integrity, etc. ... View more

Since you see one optimal behavior in ArcMap, and another degraded behavior in Pro, please report this to Esri Support.  We would like to take a look at how the applications handle certain data/workflows differently and improve them where we can. ... View more

I was not aware that the Enable Enterprise Geodatabase tool could (should) be used on SQL Server express instances, which can only house Workgroup and Desktop geodatabases (not enterprise). Just open ArcCatalog, connect to your SQL Server Express instance and create a new geodatabase. ... View more

Those SDE_GEOMETRYnn tables are created when you create feature classes using GEOMETRY storage.  Its a method to store CAD style data.   Where are you pasting this data from?  Does it contain data, and if so does that data have CAD like data (true curves)? As a temporary workaround, and test, can you create a new blank feature class in your SQL Server database, in the feature class creation import the spatial reference and fields from the source data.  When the feature is created, can you then load the data using simple data loader?   Workflow: Connect to SQL Server in ArcCatalog. Create new feature class->  import spatial reference and fields from source data.  Create the feature class using GEOMETRY spatial storage. Right click the new feature class-> Load-> load data.  Import the data from the source feature class. ... View more

In ArcCatalog, ensure that the privileges for those users on the data have not changed (when things go wrong I like to DOUBLE check what I think I already know). In ArcCatalog connect to your Oracle database, find any one of the features classes/tables that the users cannot edit .  Right click the feature class (if the data is inside a dataset then you will right click the dataset), manage-> privileges.  Make sure those users have all four update options selected. Double check if this data is in any relationship classes or networks.  If they are, and are the origin of the relationship/network, then you may be breaking referential integrity trying to delete records.  If this is this case... are you familiar with Oracle logs and tracing?  I'm sure we could get more information with a trace. Call Esri Support if you need more assistance (888-377-4575) ... View more

Have you tried copying this to a drive without parenthesis in the name? I just did a quick test. Input data= E:\test\Mydatabase.gdb Output=E:\test\My)Folder. ^those parameters have an error in the gp tool. If I create a folder named MyFolder instead of My)Folder, then it works... ... View more

First, check what type of geometry your slow feature has.  In ArcCatalog open the feature class properties and check the general tab.  See what type of 'Storage' you are using in the Geometry Properties section.  It will say something like Esri binary (aka sdebinary) or Geometry.  To create a new feature using the alternative storage stype just copy and paste the feature class back into the same geodatabase.  When you paste the feature class into your geodatabase you will see a drop down list for Configuration Keywords in the Data Transfer window.  You will choose the alternative storage type here. This pasted data will not be versioned, but should maintain related data (things will be pasted in with the _1 naming convention).  It may be worth it to add this unversioned data to ArcMap and test the performance first.  Once you have observed the behavior of this new unversioned data, register it as versioned and test again. A lot of performance issues have to be tested in a manner that incrementally adds on functionality, with testing in between each workflow.  It is tedious, but worth it if you want to find the root cause. ... View more

https://community.esri.com/groups/geodatabase?sr=search&searchId=d4b0281c-4ab3-4447-bae8-e8fe439ae361&searchIndex=0‌ ... View more

This may answer your question... A quick tour of working with nonversioned data—ArcGIS Help | ArcGIS Desktop  "Editing nonversioned data that is stored in an enterprise geodatabase is the equivalent of performing standard database transactions. You perform a transaction within the scope of an ArcMap edit session. You start the edit session and perform the required operations, such as adding, deleting, or moving features and updating attributes. When you save your edits, the edits you made are committed to the geodatabase as a single transaction. If you don't want to commit the changes to the geodatabase, you must quit the edit session without saving. This eliminates all the edits you made since you opened the edit session or since your last save. Each transaction can include as few or as many operations as required, provided they fall within a single edit session. When you edit nonversioned data in an ArcMap edit session, you edit the data source directly; nonversioned edit sessions do not store the changes in other tables like versioned edit sessions do. This avoids the overhead of managing these extra tables and allows you to easily adapt third-party applications so that they can read and edit the data. However, the drawback is that since you edit the data source directly, you cannot undo or redo an individual edit if you make a mistake. The only way to undo edits is to undo all edits by quitting the edit session without saving." ... View more