Latest Contributions by ThomasColson

That is not a very effective workaround when dealing with many holes. Looking forward to this critical functionality showing up in the next release.  ... View more

Kory Kramer‌, see my post in EAP on this topic, and my suspicion of the cause of the performance problem.  ... View more

SQL4? I have not heard of that version, that might be the problem? Microsoft SQL Server database requirements for ArcGIS 10.7.x and ArcGIS Pro 2.4—Help | ArcGIS Desktop. How far away on the network is your server? What happens when you disable versioning and hit the parent version? The bug I'm thinking of doesn't apply in this case, though, sounds like a call to tech support.  ... View more

I recall a bug about this, when hitting a feature service. What is the exact data source, including versions, etc. For example, SQL 2014 Enterprise Feature Class, not versioned, archived enabled, pushing a server 10.6.1 feature service with Windows Authentication......that level of detail.  ... View more

Local drive: Great performance, no functionality in a networked large organization; Network: Pro is slower than the tape drive on a TRS-80 but the good news is you can slowly collaborate with other folks in the org You should  never use One Drive, Google Drive, S3 Bucket, etc....as a "live" data source in Pro or Arc Map. To much latency regardless of your bandwidth.  ... View more

Attribute rules mimic the functionality of the native spatial functions in SQL. I used to do extensive geoprocessing through the use of triggers, but the Pro requirement to enable archiving in order to support offline editing rendered all of that obsolete. I recently discovered how to use Introduction to attribute rules—Geodatabases | ArcGIS Desktop  to do spatial data management operations on the fly, and am quite happy with the functionality. Regarding editing the data in SQL directly, while supported by ESRI, strongly discouraged due to the interdependence on other parts of the enterprise architecture. I only do it when needing to perform surgery on a DB, and actually have a case open right now and am waiting ESRI approval to edit a SQL table directly.  How To: Insert geometry from XY coordinates using SQL  is a good example of how to to bulk inserts into SDE ... View more

I wouldn't recommend a touch screen for Pro, unless all you do is very very very casual and infrequent GIS work. Pro doubles, and in some cases, triples, the amount of mouse movements and button clicks compared to arc map, and you'll quickly grow frustrated with the swiping.  ... View more

I recently had an experience with someone wanting to put Pro on an "Affordable ASUS" and the conclusion was "If you need this software to perform your assigned duties tell your supervisor to get you a computer that will run it".....I'm sure a budget ASUS will "Start Pro", but IMHO it will be a miserable experience. The NVIDIA dedicated card will be the deal breaker for you. Get the biggest you can afford.  ... View more

Maybe deploy that on Git? I can see quite a lot of folks using Git to collaborate on scripts used for benchmarking Pro using perfstat. But it would be helpful if someone more knowledgable started that off. I don't know enough about Git or scripting to pull that off. ... View more

I've looked at that as a specific resource for this very topic, and wonder, is there a generic Perftools script that can be provided, similar to the "Can I run it" software checker ESRI uses?  ... View more

I am a long ways from rolling over this new attribute rule thing, and will probably limit it to the .001% of my data that I can completely manage in Pro.  ... View more

We use both platforms, but use Portal and Web Application Builder apps to replace most of what users were needing desktop for. I say "most", as most editing and data management functions can be performed in a WAB. Some of the new stuff in AGOL, that is not yet in Portal WABS, like move a point using an XY value, is sorely needed but our upgrade path is pretty slow. My unrealistic, unicorn rainbow dream is to completely eliminate desktop all together. If we look at all other business applications that 90% of an org's users need for 90% of that org's work, it's all web-based. When I say web-based, I mean the application itself is a web app, not porting Pro through HTML-5 clients from AWS remote app hosting, because then I'm still managing Pro. Some internal discussions (at my workgroup level) have hinted that I better find a solution in that direction, as spending 5 or 6 figures on GIS computers every 4 or 5 years will never happen again. Why do you need GPU video cards and lots of memory? The budget and the HR people can do their jobs perfectly fine with web apps..... If I use WAB Developer Edition, I can move a few more folks to web only, but we're discouraged from "Writing custom applications".  ... View more

Pro is the reason. Here's a short version of a very long story: Back in the ArcMap, un-federated server days, we accomplished a LOT (90%) of routine data management with triggers. We're collecting thousands of new points weekly, and most of them have a very long list of what we call "Administrative Boundary" requirements: "What state is this in? What District is this in? What Watershed is this in? If it's above 4000' elevation, it gets this attribute". For our core data standard, there are about 20 of these, with some protocols (e.g NWI wetlands) having 30. SQL triggers handles most if not all of these spatial queries since we were using versioned: move edits directly to base with no child versioning. The important thing here is that this worked with ArcGIS Server Offline Feature Services (Right click, download local copy for editing), as being able to edit a feature service directly has never been, and never will be, an option for us. It's not a bandwith issue, it's a concurrency issue, and that's as much as I want to say about it.  Now Pro.  In order to be able to take feature services in Pro offline, we have to enable archiving on the SDE feature classes. Managing Archiving AND Versioning turned out to be a nightmare. So away went the versioning. Turns out with just Archiving, SQL triggers cause all kinds of havoc. We found other non-GIS issues related to triggers in this workflow, and have since banned them, as we also hang related non-GIS tables off the versioned-views (business table) and found the triggers are also breaking referential integrity. I've replaced the triggers with even more complicated python tool boxes that mostly automate everything, but still require the unhappy user to have to select something and push a button, whereas in the past, it was 100% automated. And the python witch magic is only available to my shrinking population of desktop users, as we're drinking the Kool Aid and pushing everything we can to Portal and WAB's and yanking access to desktop, because we can't afford the hardware requirements for Pro.  Take home message:  I used to think myself very clever for all the SQL scripting I did to make the triggers work, some of them very complicated. Now whenever something goes wrong in SQL, people wander around with bloodshot eyes for days muttering "Colson's damned triggers", and I covertly delete them and reply "nope, it was a hard drive failure, fixed it!".  So we're back full circle, and it looks like Attribute Rules will do the same thing. Yay for attribute rules.  ... View more

Did this ever get answered? We're looking to deploy to HA groups and SQL, and this looks like quite a barrier to that working.  ... View more