Select to view content in your preferred language

Finding Who is Data Owner

2386
6
02-15-2024 04:50 AM
Labels (2)
CodyPatterson
MVP Regular Contributor

Hey All,

ArcGIS Pro 3.2 ArcGIS Enterprise 11.2 & Geodatabase 11.2

Recently, we have enabled transactional replication between two database systems, and we're attempting to setup the data as presented in the previously used database.

Currently, I would like to setup Subtypes through data design, but this is what I see:

CodyPatterson_0-1708001353895.png

 

I was curious if it may not be registered with the geodatabase, so I attempted to use the tool:

CodyPatterson_1-1708001385284.png

In the case of transactional replication, who is the data owner, and how can I make these changes? I'm signed in using sa and am the owner of the data itself.

Everything is also read-only:

CodyPatterson_0-1708001548602.png

 

Thanks in advance!

0 Kudos
6 Replies
George_Thompson
Esri Notable Contributor

Based on the screenshot, it looks like SDE is the data owner. You would need to connect as the SDE user to make the changes.

It is also not recommended to have data owned by SDE.

Can you provide some more info if SDE is not the data owner?

Even connecting as SA does not allow you to make some changes within the Pro client.

--- George T.
CodyPatterson
MVP Regular Contributor

Hey @George_Thompson 

I ended up attempting to connect with SDE and it still referred to me as not the owner. I attempted to create a DBO role and made some more progress, but now I'm facing this:

CodyPatterson_0-1708008674017.png

 

Maybe some good progress?

0 Kudos
George_Thompson
Esri Notable Contributor

I am not sure what would be next, since it seems that the layer is already part of the geodatabase so trying to register it is not a path forward.

Are you sure that the database is already enabled as an Enterprise Geodatabase? 

Based on the screenshot at the top, it looks like this is a view?

How was the SDE user created?

--- George T.
0 Kudos
CodyPatterson
MVP Regular Contributor

Hey @George_Thompson 

For some reason, the actual feature class image won't display unless I view the indexes once and refresh the geodatabase. This is what it looks like normally:

CodyPatterson_0-1708013738066.png

 

The SDE user was created prior to transactional replication mirroring the SDE user on the publisher side.

As far as I'm aware it was already a Geodatabase, I wouldn't be able to create feature classes if it were not to my understanding.

Cody

0 Kudos
MarceloMarques
Esri Regular Contributor

@CodyPatterson - see the Database Connections Best Practices from my community.esri.com blog for more details. The recommendation is to never use the sde user to load the data, the sde user is the geodatabase arcsde repository owner, and the sde user shall be used only for the geodatabase administration tasks. You need to create a data owner user to load the data. For more details read my database guide book for production mapping on SQL Server available in my community.esri.com blog, see link below, you will also find there the database template scripts for SQL Server to help you setup the SQL Server Geodatabase following the best practices.

Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices

I hope this helps.

| Marcelo Marques | Esri Principal Product Engineer | Cloud & Database Administrator | OCP - Oracle Database Certified Professional | "In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger." | “ I do not fear computers. I fear the lack of them." Isaac Isimov |
0 Kudos
CodyPatterson
MVP Regular Contributor

Hey @MarceloMarques 

Thank you for the resources and links to your posts, I'll give them a read and absorb as much as I can! I agree that SDE shouldn't be used other than the administrative tasks as you've mentioned, but I'm inheriting this database from another user in a similar position and am currently working to piece everything together. We ended up enabling versioning on our datasets and chose to do the Create Replica task as well, as far as I'm aware this will not continue to sync like the transactional SQL replication would, so we more than likely will need to setup recurring replication.

Just how it goes though, there will be limitations in anything seemingly!

Cody

0 Kudos