|
POST
|
Hi John, You should certainly see good performance if you place the data in a file geodatabase that resides on the same machine that ArcGIS Enterprise does. That would be the best scenario unless you could get your enterprise geodatabase on that same machine as well. But if the enterprise geodatabases are in a data center 2 states away, you'll always see a performance hit there vs. using a file geodatabase locally. There's only so much you can do to combat network latency. Jonathan
... View more
08-30-2018
11:04 AM
|
2
|
0
|
1218
|
|
POST
|
Hi Stephen, OK, that works as well as a way around this! We have lots of documentation on versioning. It can be complex for the first time user but it isn't too bad once you work with it for a bit. An overview of traditional versioning—ArcGIS Help | ArcGIS Desktop Start with this link above and then use the navigation on the left side of the page to click through all the other pages on versioning after this one. We also offer an instructor led course on this if you want to go all out: https://www.esri.com/training/catalog/57630435851d31e02a43ef9c/implementing-versioned-workflows-in-a-multiuser-geodataba… Hope that helps! Jonathan
... View more
08-27-2018
01:22 PM
|
0
|
1
|
4029
|
|
POST
|
Hi Stephen, You are correct, you don't want to delete that State_ID from the database level as that could cause corruption in the geodatabase. Really, you need to do a reconcile, post and compress which should remove that State_ID from the States table as long as it is unreferenced at the time of running the compress. That is the only acceptable way to do this from our standpoint. I'm assuming that you have child versions off of Default with edits in them? Do you still need those versions once they are reconciled and posted with Default? If not, you could rec and post all of them, delete them, and then compress which should remove this State_ID (make sure to stop all services hitting this geodatabase as well). Geodatabase compression—Help | ArcGIS Desktop Jonathan
... View more
08-27-2018
11:58 AM
|
1
|
3
|
4029
|
|
POST
|
Hi Michael, Yes, it would. So that is certainly a possibility here and something to take a look at. Jonathan
... View more
08-22-2018
07:43 AM
|
0
|
1
|
1935
|
|
POST
|
Hi Kelsey, You are correct, deleting the versions is one method of getting a full compress done. The method I laid out is the other way. If you still have states being referenced after going through this workflow, we'd need to dig deeper into why that is. That may be better handled with a case with Tech Support. Full compresses are necessary when you need to unregister a feature class as versioned or maybe you are seeing some performance issues and you want to make sure all your delta tables are empty to rule out something there. There could be a few reasons why you'd want to do it. But there are organizations out there that never get a full compress done because it just isn't possible for them. And that's OK. Let me know if I can answer anything else for you! Jonathan
... View more
08-22-2018
06:54 AM
|
0
|
3
|
1935
|
|
POST
|
Happy to help! Let me know if I can assist further as you research this.
... View more
08-22-2018
06:50 AM
|
0
|
0
|
1677
|
|
POST
|
Hi Kelsey, I don't think you are missing anything really. Your geodatabase maintenance strategy looks good, I see no issues there. The only question I have is, why are you deleting the versions? Are you going for a full compress each time you run this? I ask because it goes into your second question. Having to re-register all of those child version connections with Server is expected. See this note below that we include on our page on the topic: "If the database you register contains a versioned geodatabase, ArcGIS Server accesses the version of that data present in the geodatabase version you set for the connection file. If you want ArcGIS Server to access different versions, you must register separate connection files to connect to these geodatabase versions. For example, you may need to register one connection file that accesses the Default geodatabase version and one that accesses a child version." About registering your data with ArcGIS Server—Documentation | ArcGIS Enterprise So given that, it seems like deleting the versions each time may not be the best way to proceed. There is a way to get a full compress done without deleting the versions if that is the goal. But getting a full compress done each time you do this is also not necessary. Reconcile and post all child versions to Default Re-reconcile all child versions to Default (without posting) Save edits Compress Doing the above will also get you a full compress if that is the desire and also not delete those versions which means you won't need to re-register databases with Server. Jonathan
... View more
08-21-2018
02:28 PM
|
1
|
5
|
1935
|
|
POST
|
Hi Alfonso, There is a lot of ground to cover in your question because there can be a number of reasons why an organization may want to publish a hosted feature layer vs. reference the data in the geodatabase. I'm including our documentation below which does a good job of explaining most of this. If you have any specific questions after reading through, feel free to let me know. I do want to clarify one thing you mentioned. When you choose to publish data and reference the data in the data source, you aren't actually loading a geodatabase onto the ArcGIS Server machine. Your enterprise geodatabase will still reside on the machine you install the database instance on. When you register that geodatabase with ArcGIS Server, you are setting up a communications pathway where Server can access the data in that geodatabase as needed. So when you publish and choose to reference your data, a web layer is created and it just references the underlying data sitting in the geodatabase. I hope that makes sense. Data and publishing in ArcGIS Enterprise—Portal for ArcGIS | ArcGIS Enterprise Hosted layers—Portal for ArcGIS | ArcGIS Enterprise Jonathan
... View more
08-21-2018
02:09 PM
|
1
|
2
|
1677
|
|
POST
|
Hi Preston, OK, thanks for that information. If this is specific to one feature class and occurs regardless of a new MXD or not, I'd like to try creating a new feature template. Organizing feature templates—Help | ArcGIS Desktop Creating new feature templates—Help | ArcGIS Desktop The second link above goes over how to create a new feature template. Can we try that and see what happens? Jonathan
... View more
08-21-2018
11:40 AM
|
2
|
0
|
1065
|
|
POST
|
Hi Preston, A couple of questions here for you: Just to be clear, are you using a file geodatabase or an enterprise (SDE) geodatabase? They are 2 separate things so I want to confirm. What version of ArcMap are you working with? Does this happen with a brand new MXD or is it specific to an existing MXD? Are there other layers in this MXD that exhibit the same behavior or just this one? That should help narrow it down a bit. If this is specific to this one MXD, you may try repairing the MXD with the MXD Doctor utility that comes with your install of ArcGIS. It is located in the Desktop Tools folder in your install location. Jonathan
... View more
08-21-2018
07:33 AM
|
0
|
2
|
1065
|
|
POST
|
Hey Tom, This is a known issue. But can you confirm that this is your workflow? Add Hosted Feature Layer to a map in Pro Open the attribute table and sort the table based on a field which has a domain Scroll down through the table with your mouse, you should see the error Here is the bug information: BUG-000106410: Sorting a hosted feature layer on a Domain field and.. If your workflow is different, it would be good to know. We'd want to get a new case created in Support and investigate that. Could be we'd need to update this bug or create a new one. But I think this is the bug you are running into. Jonathan
... View more
08-16-2018
11:53 AM
|
2
|
8
|
7529
|
|
POST
|
Hi Todd, You are correct, the Import Map functionality in ArcGIS Pro does not actually move the data anywhere. So if I have a feature class in an MXD that is coming out of an enterprise geodatabase and I use the Import Map functionality in Pro to import the MXD, my data is still in that same enterprise geodatabase. We aren't creating a new connection in your Pro project to that enterprise geodatabase and sourcing the data from there. Hope that makes sense. Besides the usual ways to re-source data in Pro, have you thought about using Python? If you have legacy MXD's with a lot of layers and symbology setup that you don't want to recreate in Pro, you can use Import Map and then use Python to resource all the data. Updating and fixing data sources—ArcPy | ArcGIS Desktop Once you wrote one script, it would probably be easy to tweak it a bit for each Pro project. But I am not aware of any tools we have in place to do this at the moment. Jonathan
... View more
08-14-2018
10:07 AM
|
1
|
1
|
1913
|
|
POST
|
Jimmy, Can you reproduce this outside of the Utility Network Management Extension? With just a standard feature class published as a feature layer in Pro?
... View more
08-13-2018
02:24 PM
|
0
|
0
|
3606
|
|
POST
|
No, it isn't. I certainly can't get a field to restore using the undo button after being deleted in Pro.
... View more
08-10-2018
07:40 AM
|
1
|
1
|
13096
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-10-2018 07:40 AM | |
| 1 | 10-03-2018 08:28 AM | |
| 1 | 04-12-2018 01:47 PM | |
| 1 | 01-24-2019 07:35 AM | |
| 1 | 01-03-2019 07:56 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:24 AM
|