nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Relationships to non-geodatabase enabled db/tables

WarrenMedernach

Can non 'geodatabase enabled' db tables be related to a different geodatabase where the spatial features reside?

IOW, I have an existing/established database with applications built around this db (Database A), and I would like to now relate this data to some spatial objects in another geodatabase (Database . I'm not sure if I want to 'geodatabase enable' Database A and would prefer to create the spatial objects in Database B and establish the relate back to Database A.

Is this a supported workflow? Suggestions/ideas greatly appreciated.

Warren

Finde mehr Beiträge mit dem Tag

Accepted answers

JakeSkinner

I would recommend having a scheduled export/replication from the database to the geodatabase.

All comments

JakeSkinner

Hi Warren,

You could create the relate in the MXD by right-clicking on the feature class > Joins and Relates > Relates. This relate will only exist in the MXD. You will not be able to create a relationship class from the feature class to the database table. Both the feature class and table would need to exist in the same geodatabase in order to create a relationship class.

WarrenMedernach

Thanks for the quick response Jake. That's not what I was hoping to here, but at least I know it's not supported. In the end, I would like to be publishing this data so relationship classes will be required.

I'm curious then, what is the workflow for large organizations when they want to consume existing attribute data tables that reside in corporate databases where there is no way the database would be allowed to be 'geodb enabled'? I can't be the only one who has wanted to attempt this sort of configuration? Am I missing something, or some other way to do this?

Warren

JakeSkinner

I would recommend having a scheduled export/replication from the database to the geodatabase.

WarrenMedernach

Aaaah, that makes sense... probably a more secure/robust method as well.

Thanks again for the quick responses Jake!

RandyKreuziger

Why not create a database view in the geodatabase joining data from the geometry field(and any other attributes from the feature class) to attributes from a table in the non-spatial database? We do this all the time. It does require guest permissions on the data in the non-spatial database.

Having said that, we also have scripts scheduled weekly to create standalone feature classes from non-spatial databases. It all depends on the use and the needs of the GIS users.

User35489

Hi,

Similar scenario discussed in below thread. Have a look at it.

https://community.esri.com/thread/171929

Regards

WarrenMedernach

Thanks for the additional info Randy, Abdullah.

I believe my scenario is a little different, and should be even simpler. I simply want to create a relationship class between a feature class in my geodatabase, and a 'data table' residing in a different database. This is a 1:M relationship so doing a straight join is not what is required.

I'm not really sure what I'm doing wrong, but I have NEVER had any success getting ArcGIS to recognize SQL Server Views for a relationship class. It doesn't seem to matter if it is a regular view, or materialized/indexed view, the 'Register with Geodatabase' is always grayed out.

I will be attempting the replication method here shortly.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.