Latest Contributions by George_Thompson

https://community.esri.com/groups/geodatabase?sr=search&searchId=f37732f7-cad4-4997-809f-7ce967d93aa2&searchIndex=0‌ https://community.esri.com/community/gis/managing-data?sr=search&searchId=11943c08-d75b-4637-bbf0-cfab66fe4f4f&searchIndex=0‌  to add some more eyes on the question. ... View more

I am fairly sure that you must have ArcGIS Enterprise licence to create and Enterprise Geodatabase (EGDB), of any flavor. Having Pro just gets you the UI to create the EGDB not license it. -Have you authorized an ArcGIS Enterprise (Windows and/or Linux) site yet? ... View more

Geodatabase‌ ArcGIS Enterprise‌ Managing Data‌ This is from the help documentation on 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

Hi Chris - You asked this question in the GeoNet Help section. You may want to move it to another group like: https://community.esri.com/groups/technical-support?sr=search&searchId=d1ec750c-2911-4634-8007-1a997631ae76&searchIndex=0 https://community.esri.com/groups/geodatabase?sr=search&searchId=e8e248f8-cae1-4aa5-af3f-3d82a508d19c&searchIndex=0 Can you also add the following related information: -What version of ArcGIS products are you using? -Where is the source data located? (i.e. file Geodatabase, Enterprise GDB, etc) -What file type is the joined data? That defect that you list, NIM058535, was fixed at 10.1. ... View more

I would say yes. There needs to be no spaces in the file path location. ... View more

Look at this Tech article: Error: Attempt to configure data store failed. Extended error message: Failed to configure tile cache data store  Focus on the solution section. ... View more

https://community.esri.com/groups/geodatabase?sr=search&searchId=9895f743-0c74-4fbd-a0bf-8230ff42322a&searchIndex=0‌ https://community.esri.com/community/gis/managing-data?sr=search&searchId=733b7761-49c4-4a19-a631-dc8961eb65f1&searchIndex=0‌ ... View more

Please mark the answer as correct for others to find ... View more

As for the GDB_Items table (or any GDB/SDE_ table for that matter) is a system and should not make sense, for most people You may be correct that some of the relationships were created in SQL Server and not ArcGIS. If that is the case, then the ArcGIS client would not know of them and you would be required to transfer them via SSMS. ... View more

I am not sure on the SQL Server side what is created. What happens if you just copy over the feature class with the relationships to the new EGDB? ... View more

You will not find the relationships in SSMS or the root EGDB in SQL Server. These are objects that ONLY exist in the Geodatabase and in the ArcGIS Client. Look at this help: Copying feature datasets, classes, and tables to another geodatabase—ArcGIS Help | ArcGIS Desktop it talks about relationship classes. ... View more

As you found out you cannot change the name of the SQL Server database once created. This is also true if you have a second instance of SQL Server, the DB name must stay the same always. No matter which of the methods you use to move your SQL Server database, you cannot rename the database. When you restore a database, for example, you are given the opportunity to restore it with a different name. Don't do this with a geodatabase; you won't be able to connect to it. Here is the documentation on the ways to move SQL Server DB's: Methods to move a geodatabase in SQL Server—Help | ArcGIS Desktop  Copy/Paste into a new SQL Server EGDB should not impact the relationships and carry them over. If the data is versioned, it will only copy over the data for the version in which you are connected. Hope this helps! Geodatabase‌ ArcGIS Enterprise‌ ... View more

Adding a broader audience: https://community.esri.com/groups/geodatabase?sr=search&searchId=a5565455-889d-4f1d-b7e3-3fed728ddfe6&searchIndex=0‌ ... View more