Latest Contributions by DuarteCarreira

Ezi Molley‌ I completely agree with you. And I'm going to vent a bit more now... This is not a very specific case scenario where we have to help debugging the situation and provide as much reproduceable data as we can to tech support. arcgis pro does not fit in that situation. We are not talking about exotic setups or workflows. Everyone knows pro runs badly always. This is basic QC responsibilities and someone is knowingly let the product get out to the public like this.  Any guy/girl at esri with a common PC will encounter the same issues we are all facing easily. Please don't tell me you don't know about network performance or you didn't detect the glaring rendering and geoprocessing issues. Don't tell me you don't make performance baseline testing. I know you do. Just look at the excellent System Design Strategies site. It's all there. So to me this is a question of honesty and transparency.  So my message to esri is this... own it.  In truth, arcgis pro is free of charge. So there's a tolerance for a slow, informed, programmed switch from arcmap. Key is informed... Stop avoiding the real situation and start showing good leadership. Tell us what you intend to do about it, even if it's nothing at all. You could tell us that it's an intrinsic characteristic of the new software, and it will be slower than arcmap for some hardware generations to come, that eventually will catch up.  Just like going from av3 to arcgis 8 back in 1999 (it was staggering slower). Tell us to buy real top-end machines, with raid nvme disks, cgi pro video cards, max frequency 2 slots cpus with 20 cores, and min 128gb ram.  At least we wouldn't be surprised that pro doesn't budge on our measly i7 sata sdd 32gb rigs. We wouldn't waste our money like this anymore. And/Or you can tell us that you have an optimization plan going on and will include performance improvements in each iteration of the following releases. And, please, in either case, create a knowledge base document on how to mitigate the existing performance issues. That would be helpful.  You can start by acknowledging the problem and point to the road ahead to solve it. Be a leader. That would win over *all of us* instead of alienating most of us. ... View more

I've been looking at pro for the last years. Always same conclusion: that it is too slow (mind-blowing slow). I remember going from arcview 3 to arcgis, and this is not the same user resistance issue. As an arcmap user I had the same wish list as everyone else: - multithread - to speed things up with my multi-core cpu Result: pro is unbearably slow - antialiasing - to see things as they print or make better presentations Result: it does anti-aliasing, but is so slow I can't use it - 64 bit - I want to use more memory to be faster! Result: pro is unbearably slow - several layouts in a project - I want to be more productive, have less projects for a single task Result: pro is unbearably slow - cartography/symbology - I want better/more rules so I am more productive and can avoid complex layer/scale range/symbology setups (same layer loaded multiple times, different query defs, scale ranges, symbols) Result: pro is unbearably slow So the result is - I can't get the good stuff that would make me abandon arcmap. As time passes and arcmap gets further behind I'll be looking at the competition for a new best-in-class GIS desktop product. I already found one that offers all of the above items (QGIS). If esri doesn't/can't make a good product I will move on. I'm a client, I am not a fan. I owe you money not loyalty. You owe me quality service. ... View more

Hi there. Bit late, but I use the truncate/append method a lot and it works fine. I also reindex every index on the Feature Class (there's a tool for that too). As long as this is a readonly mapservice this works fine with a small window of oportunity where a user may see an empty or incomplete dataset while the process is running. But I feel this does not answer the original question: schema locking does not block editing. It blocks adding/removing fields and deleting the feature class. Truncate+append allows to reload the entire feature class with data from scratch. The added benefit is that any views that depend on the feature class are kept safe and keep working fine. As opposed to deleting and recreating a feature class will delete all views that use that feature class. ... View more

Same here... did you get over this? ... View more

I have now upgrade postgresql 9.5 + esri 10.5.1 to esri 10.6. st_raster type and functions in sde schema are not deleted. This means it is not possible to upgrade to postgresql 9.6. ... View more

I was trying to go from 9.3 to 9.6 and that's impossible without the dll for 9.6. So now I've done the upgrade from 9.3 to 9.5, keeping with geodatabase at 10.5.1. The next step is to try upgrade that geodatabase to 10.6 and see how that goes. Hopefully arcmap will automatically remove all traces of st_raster, and I'll be able to delete the dll. Only then will I be able to upgrade postgresql from 9.5 to 9.6. Note that arcgis 10.6 does not support postgresql 9.3 so I had to ugprade postgresql. ... View more

I'm sorry I must not have been clear from the start. The problem only appears when you have a geodatabase with st_raster installed. Which is my case. When I heard st_raster was to be discontinued I moved all raster out of the database. But the sde system types and functions, etc., still exist. Hence the difficulty to upgrade without i) removing them or ii) having a 10.6 dll. Thanks for your comments. ... View more

arcgis creates a series of objects in the sde schema that depend on that libst_raster_pg.dll, namely the st_raster type and a series of st_* functions. Once you delete the dll all of these will provoke errors in postgresql. Also, if you deleted the dll, in the future when you try to upgrade say to postgresql 9.6, the missing dll will prevent restoring of objects that depend on the missing dll. Also, you will not be able to use pg_upgrade - the preferred way to upgrade postgresql - since all binaries must be present in both versions - the old and the new. I hope the recommended way to upgrade a geodatabase is not to "brute force delete" a library in use by objects of the geodatabase. ... View more

I don't have any raster data and config word is not st_raster. My doubt is what to do with the libst_raster_pg.dll I have on the lib folder that's v 10.5.1. When upgrading we're told to replace esri's dll's with the new versions. so st_geometry will be replaced with the new 10.6. But what about libst_raster_pg.dll?  Thanks ... View more

So, it seems federated Server security is handled by Portal. So no, rest end points shouldn't be public. Should be protected by portal's security, IWA or otherwise. Couldn't find any reference to server REST api endpoints changing, other than the tokens url, which changes to portal. I figure public js api web apps to keep having access must use "the" proxy with included credentials. This bread and butter kind of stuff is really not clear or easy to find. I can get more info on high availability scenarios than on simpler things. Maybe it's  just me, but I find docs very confusing, spread over many, many seemingly unrelated pages. I still can't figure a simple, to the point, conclusion of how IWA/security works... I can get a step-by-step to configure it but can't get a good picture of what it causes... So on to testing in a vm the whole thing... hours and hours of fun await. ... View more

Sorry to only answer today... just noticed your reply now. I wouldn't consolidate 600 layers. But testing is always best. If you have 96GB ram and that's not a limitation yet, than don't consolidate into a single mxd. Maybe study what would be an intermediate consolidation plan. Hundreds of seldom used services sounds like a nightmare. Could they be put into a single or a few mapservices? I use MXDperfstat to see if performance issues exist with a single user. I don't have nearly the number of users you do. You can try to monitor mapservices statistics, like max wait time, # of failed requests, to see how things work under different configurations. /blogs/clarity/2015/09/14/tools-to-monitor-your-servers-and-services  About server statistics—ArcGIS Server Administration (Windows) | ArcGIS Enterprise  To simulate 10 simultaneous users you can use a web stress tool, and see how the server responds to increasing users. esri has one, I never tried it since it seems a bit overkill to me: http://www.arcgis.com/home/item.html?id=e8bac3559fd64352b799b6adf5721d81  There are lots out there... I've used JMeter in the past. As you test your mapservices keep an eye on the server's CPU, memory and bandwidth usage. You'll get an idea of what your bottleneck is/are. Also be aware that your testing PC should not saturate CPU or bandwidth. If it does, divide your testing into several PCs. ... View more

It would be reasonable to assume documentation about choosing arcgis server security model would advise on what does not work with each option: Configuring ArcGIS Server's authentication tier—ArcGIS Server Administration (Windows) | ArcGIS Enterprise  I have been working up to having web tier with windows authentication only to find out later on in a totally unrelated documentation page that printing does not work and is not supported at all: Print maps that contain secured services—Documentation (10.5) | ArcGIS Enterprise  It's on the very last paragraph... It's a discovery process with esri's "Enterprise" products. You may well find out that all your invested time was just wasted. At this point I don't know what else might not work with WIA... ... View more

Bug. https://community.esri.com/message/658246-imageparameterslayerdefs-does-not-work-with-105  Worse: regression bug on 10.5.1... ... View more