Latest Contributions by ThomasColson

SQL 2012 introduced autogrid (with 8 levels), but legacy SDE spatial tables will still use the 4-level index unless you specifically recreate the index. I've found that starting with 1024 cells with autogrid is worth at least a 10% increase in draw times for large tables. ... View more

I believe this is the default behavior of Portal with federated GIS Servers behind web-tier. The user is in fact, authenticating via IWA, but the edit user stamp is coming from when PTL passed that edit from the Portal Web Interface, or feature service local edit check in/out, to SQL. ... View more

I am also getting this, randomly, for difference services each time, even though I can access the service just fine. Can you confirm that this also falls into Esri Support responsibility? Error: Http status of 404 returned from GET request to https://services1.arcgis.com/fBc8EJBxQRMcHlei/arcgis/rest/services/GRSM_FISH_DISTRIBUTION_2015/FeatureServer/1?f=json. Error: Layer ( https://services1.arcgis.com/fBc8EJBxQRMcHlei/arcgis/rest/services/GRSM_FISH_DISTRIBUTION_2015/FeatureServer/1 ) could not be harvested. Please see other messages for details. ... View more

This "could" be related to your use of a Domain Service account on ArcGIS SVR and/or SQL, and is related to the Server Principal Name not being registered in Active Directory. Try registering the SPN for SQL How to Configure an SPN for SQL Server Site Database Servers and see if that works. ... View more

I too am getting this error, very frequently, but very randomly. At any time, up to 20% of my organizations open data  is not discoverable due to this, which is precluding me from using Opendata until it's more stable. Any idea on when there will be fixes? ... View more

This is for MS SQL, but I can't imagine why it won't work in Oracle: Re-order Attribute Domain Values ... View more

Hmmm....the exact syntax of how-to escapes me at the moment, but you'll want to include some sort of distance or predicate filter that prevents searching of every county for every tornado, or vice-versa...maybe throw a join in there? Eg. in MS SQL: PARKDISTRICT = COALESCE(f.District, p.PARKDISTRICT)     LEFT OUTER JOIN DISTRICTS AS f   ON f.Shape.STIntersects(i.Shape) = 1 or maybe a cross-apply where TOP 1 stops your search as soon as it gets a result CROSS APPLY (SELECT TOP 1 FULLNAME, shape                     FROM dbo.GRSM_ROADS  /****** force spatial index hint ******/  WITH(index ([GRSM_ROADS_idx]))                    WHERE GRSM_ROADS.Shape.STDistance(i.Shape) IS NOT NULL                    ORDER BY GRSM_ROADS.Shape.STDistance(i.Shape) ASC) as J Again, unsure of how Oracle does it, but world of difference in MS when you force a spatial index hint. ... View more

Tilting at windmills here, but could you control the value that "should" be in the column/row with a trigger on the base table? Perhaps an AFTER/UPDATE trigger? ... View more

My knee-jerk reaction is that you're seeing slow performance on the view/query layer because there's no index on the backend view. True, when you create a query layer, it asks you for a uniqueid,but that's a fake (Esri) index that is only recognized by ArcGIS. When that data is requested, and ArcGIS passes it to Oracle, the database engine is what's packaging the data. Coupled with the fact that you're also doing a spatial query, give you a few pressure points where even the default indexing options could be in fact worse than no index at all. It's been a billion years since I used Oracle, but look into where you can tune the spatial index on both of those tables, add a unique index to the view, and add a non-clustered index on all of the columns being consumed by the view. ... View more

Re: Converting from SDE Views to Regular SQL Views - Any Gotchas? Might help out here: in essence, creating the view via SSMS bypasses all of the dependence on the SDE command line utilities. ... View more

I've come to be pretty dependent on both Geometry and Geography storage types, given that I can do significantly more automated data management and processing with them both. Knowing that I'm taking a performance hit by using them, there are a lot of tuning options available, which I've managed to get Geography performing as well, if not faster in some cases, than binary. The biggest gain comes from tweaking the spatial index​, but there are other gains from adding other non-clustered indexes and or statistics based on specific use. As for view performance, one can force indexes on a view at creation with schemabinding: CREATE VIEW [dbo].[ELKOFFTAKE_VIEW_LOCATIONS] WITH SCHEMABINDING AS SELECT OBJECTID, VERROR, MAPSOURCE, SOURCEDATE, EDITDATE, MAPMETHOD, QUADNAME, UNITNAME, HERROR, COUNTY, STATE, X_COORD, Y_COORD, LAT, LON, WATERSHED, STREAMNAME, ELEVATION, YR, NOTES, COORD_UNITS, COORD_SYSTEM, DATUM, UTM_ZONE, MANAGEMENTZONE, PARKDISTRICT, EDITBY, CREATEBY, CREATEDATE, UNITCODE, RESTRICTION, VEG_CLASS, LANDFORM, GlobalID AS 'LOC_ID', LOC_NAME,  TRAIL, ROAD, VALID_RESULT FROM [dbo].[WILD_ELK_OFFTAKE_LOC_PT] GO Then CREATE UNIQUE CLUSTERED INDEX IDX_WILD_ELK_OFFTAKE_LOC_PT   ON ELKOFFTAKE_VIEW_LOCATIONS (LOC_ID); ... View more

When you assign the Role (AD Group) to the permissions of the Feature Class/Feature Dataset, are you doing so when it is versioned? I've found that I've had to disable verisioning when applying permissions sometimes, so the permissions get applied to the delta tables upon versioning. When you say correct user id and pw, but I can't tell if you're using AD on SDE ONLY and then ArcGIS accounts on ArcGIS Server......again, I've never had much success with mixed-mode authentication in the SDE/GIS svr environment.  I'd consider switching to web tier on ArcGIS Server, and give the arcgis svr service account read/write schema on the SDE database. Your problem is definitely not the right permissions being passed from GIS svr to SQL. Turn on logging debug mode on arcgis svr and see what errors pop up when you attempt access. ... View more

I believe that is the correct behavior, and your workaround is the correct solution. Shape_STLength is a product of SDE, and is dynamical based upon the feature geometry. Since you're using M$ SQL, and you "could" be using Geometry or Geography Storage type, you could add another field and use a trigger or a constraint and auto-calculate the length: https://msdn.microsoft.com/en-us/library/bb933895.aspx ... View more

I've found, with SDE 10.3.1 on SQL 2014, for both GEOMETRY and GEOGRAPHY storage types, setting the spatial index to AUTOGRID (which give you 8 levels) and 1028 cells is a good middle-performance gain. If you're using 2014 enterprise, you could get really crazy and move some of your heavy hit spatial tables into "In Memory Tables", an experiment I'm soon to try. ... View more