Latest Contributions by JonathanFarmer_oldaccount

Hi Jordan, I'm not aware of a better method to copy related tables from a file geodatabase to an enterprise geodatabase than just to use the import method. Right click on your enterprise geodatabase connection > go to Import > Table (single). Once imported, you can relate it to the feature class.  The other option is to copy and paste the feature class from the file geodatabase to the enterprise geodatabase each time they have an update. It will take all the related items with it. You'd want to delete the existing data from the enterprise geodatabase first before doing this. I'm not sure about the connectivity between you guys and this company but this does seem like a good workflow for geodatabase replication. I'm also curious about your statement that they are adding new tables for each read and inspection? That seems like it could grow into a lot of tables very quickly. Could they not update attributes in one table?  Jonathan ... View more

Hi Jimmy, Thanks for the reply. Is this specific to one feature class (and thus one service) or can you reproduce this on multiple feature classes (and multiple services) in your PostgreSQL database? If it is specific to one, have we tried republishing to see what impact that has? ... View more

Hi Jimmy, I have a couple of things you can check here: In ArcGIS Pro, before you published, did you check the box in the attribute table options to "Show domain and subtype descriptions"? This would be for every field in the layer but a good thing to know. I also wonder if the maxDomainCodeCount could be causing an issue here? It represents the maximum number of domain codes that can be returned.Try updating this parameter to a larger value and seeing what you get. Set map service properties—Documentation | ArcGIS Enterprise  We do have some bugs on this issue for Web App Builder and Collector, are you using either of those? They are pretty specific bugs but I can get some details on those if needed. Did you apply the domains through a subtype on the feature layer? Or are you applying the domains directly to a field? Thanks, Jonathan ... View more

Hi Siran, I'm not sure why it doesn't seem to work in your environment. I just tested this on my end using 10.6.1 and the domains were included in my import. You might try one more time? If it still doesn't work, let us know your steps and maybe that will help. You could also contact Technical Support at 888-377-4575 if you'd like to work with someone here on it. ... View more

Hi Will, Esri's best practices for geodatabase administration are to have the SDE user (or the user that your organization has dubbed the Geodatabase Administrator user) perform these tasks. This is assuming that your geodatabase is an SDE schema geodatabase. Is that the case here? If you are working with a DBO schema geodatabase, then you can use a database user that is a member of the DBO schema to perform these tasks. That being said, a database user that is a member of the DBO schema, even in an SDE geodatabase, has the privileges to administer the geodatabase should you choose to do that. Here is a look at Geodatabase owners in SQL Server and the Pros and Cons: A comparison of geodatabase owners in SQL Server—Help | ArcGIS Desktop  We will always recommend that you guys use the least privileges principle when working with the geodatabase. At the top is the Database Administrator user (the SA user or member of the sysadmin fixed server role in SQL Server). They can do everything but really should be limited to 1 or 2 people in your organization and not used for geodatabase administration tasks. Then there is the Geodatabase Administrator user (the SDE user) which handles all the admin tasks such as what you are doing here. Then Data Owner roles which can create and own new data. Then Data Editor roles which can edit existing data. The Data Viewer roles which can only view data. Hope that helps a little. Let me know if I can clarify anything. Jonathan ... View more

Hi Steve, I don't have an exact answer as to why opening a Personal geodatabase in Microsoft Access corrupts the geodatabase. We document it as a possibility in our documentation but don't provide a detailed answer on why.  Understanding how to use Microsoft Access files in ArcGIS—Help | ArcGIS Desktop  However, from the Enterprise geodatabase world (of which I am more familiar), we see the same kinds of things happen when people make changes to our system tables from the database side. I've seen folks delete system tables, modify them in different ways, etc. and it all ends in having to restore from a backup. The interconnected nature of all of those tables means that modifying them in any way wreaks havoc on the whole setup. While we certainly still support Personal geodatabases in ArcGIS Desktop, I tend to recommend to folks to either move to a file geodatabase setup or a Desktop geodatabase setup (using SQL Express) to avoid these kinds of things. Just a thought as you move forward. Jonathan ... View more

Hi Steve, This isn't what you want to hear but, in my experience, there isn't a way around this error other than to restore from a backup. From looking at past Support cases we've had with this issue, all of our users have had to work from a backup when this has happened. I'm going to second what Joe said and see if your IT group can find a backup for you to work from. Jonathan ... View more

Michael, Geodatabase replication would be an option as well if that is something they want to setup.  You are correct in that the current geodatabase replication process is not supported in ArcGIS Pro. However, we'll be supporting Desktop for years to come (at least the next 5-6 since 10.6.1 releases this month and we support these products for 5 years). So I see no reason why they can't do that now. We'll have to see what the end result is in Pro in regards to replication.  Jonathan ... View more

Hi Asif, How many different feature classes from geodatabase A did you move to geodatabase B and now need to move back? I ask because if we are just talking about a few, then I would say just do a copy and paste from geodatabase B back to geodatabase A after you delete the original feature classes from A. If you want to automate this with a model or script, you can use the Append tool. The tool will allow you to input a source feature class from one geodatabase and a target feature class in another so long as the schemas match. You could build a model to iterate through the different feature classes you have.  Append—Data Management toolbox | ArcGIS Desktop  There are probably other ways to do this too but those would be easiest depending on the quantity of feature classes you are working with.  Jonathan ... View more

Thanks for the update Michael! Glad you guys got things sorted out!  ... View more

Hi Mike, Thanks for the reply. I agree with Josh's comment below that we need to narrow this down some more. It may actually be easier to have Technical Support open a case for this and investigate one on one with you. They'll be able to screen share with you and work on this in real time. You can call 888-377-4575 and we'll get a case created. I'd like to know what you see when you connect as the SDE user (or the user you guys have specified as the geodatabase admin) and then go to Administration and Administer Geodatabase. What is there under the Connections and Locks tabs? Does it match what you would expect to see (is the number of connections and/or locks correct based on who you know is connected or is there another connection listed)?  If you don't access the MXD's on the shared drive and both open new, blank MXD's from your own machines and make connections at the same time, what happens? Maybe this is related to those MXD's on the shared drive.  - Jonathan ... View more

Hi Mike, We don't have any current defects out there that would explain the behavior you are seeing here. I just did a quick test with 2 of my machines here to see if I could replicate the issue and I can't. So I've got some questions for you: Is this specific to one MXD? If you create a new MXD, does this same behavior happen? Is it specific to these 2 machines (A & B)? If you find a machine "C", does this happen there as well? You mention this does not happen on the database server machine so curious if this works. I see you mention opening an MXD and then also opening ArcCatalog. If you try this same workflow from ArcCatalog on machine A and B, does this behavior still occur? Are your users closing these MXD's at the end of their work day or when they are done with them? Are the folks on machine B attempting to access the same MXD on the same shared network drive while machine A is using it? Or are they using it at different times? Are there any ArcSOC processes running once a user closes ArcGIS completely on either machine A or B? You can see I have more questions than anything at this point. But it helps to narrow things down. Thanks, Jonathan ... View more

Hi John, This is really going to come down to personal preference, availability of hardware (on the DBMS side), and your editing needs. From a broad standpoint, using a file geodatabase certainly takes some complexity out of the equation. You don't need to purchase a DBMS, maintain it, etc. You don't need a separate server to host that DBMS or possibly need to add some resources to your desktop machine to host it. Those kinds of things make using a file geodatabase easier. But there are some valid reasons why you might need to use an Enterprise geodatabase vs. a File geodatabase. Versioning support for multi-user editing is a big one. Geodatabase replication is another function that is not available in a File geodatabase. From Esri's standpoint, there should not be a noticeable performance difference between the 2 as long as all the best practices are followed when setting up your DBMS. Things like making sure the client and database are in the same network, making sure the hardware requirements are met, etc. Hope that helps but let me know if you have any questions for me. Jonathan ... View more

Hi Robert, To follow-up on what Jake stated, we just need to make sure you are using SQL Server 2017 Express and not the Standard, Developer, or Enterprise editions. You had also mentioned that when you go through the Database Server setup wizard, it freezes? It sounds like it is freezing when you are going through the Enable Geodatabase Storage operation. If so, this would explain the error you see when you try to create a geodatabase. We commonly see this error when someone has not gone through the process of enabling geodatabase storage. So the key here is going to be confirming that enabling geodatabase storage is where the setup process fails for you, and if so, why. Once we nail that down and get things working, the error when creating a geodatabase should go away. We can try to help here or feel free to create a case with Support Services at 888-377-4575. Thanks, Jonathan ... View more