Latest Contributions by VinceAngelo

The error message indicates you have user-schema geodatabase that has not been upgraded. Once the master is upgraded, the user-schema GDBs should immediately be upgraded to the same release level. - V ... View more

If the user has overtopped the SDE tablespace, possibly not.  There are too many unknowns to make an assertion either way: Was the user assigned to the SDE tablespace? Was the SDE tablespace overfilled?  If so, was it configured as a SMALLFILE or BIGFILE tablespace? Did the tablespace max out or the disk partition fail to allocate additional storage? Have you DROPped any tables which were created by ArcGIS by SQL? Have you made a recent backup of the database, and is the archive log enabled? Have you made an extra backup of the database, in its broken state? Have you tried using ALTER INDEX .. REBUILD with a TABLESPACE option to reduce the load on the overburdened tablespace? If you have access to a more experienced DBA, I suggest you seek their guidance. -V ... View more

Tablespace management is outside the ken of ArcGIS.  Best practice is to create one or more new tablespaces to manage tables owned by users.  The SDE tablespace (or whatever has been created for SDE-owned objects) should never be used for user data -- if you overfill it, the geodatabase may fail to function. Back in the old days, tablespace management was the primary task of database administrators, and there weren't any "AUTO" options available for segment management or BIGFILE TABLESPACEs to simplify allocation strategies. Unfortunately, recent de-emphasis of this aspect means that some ugly administration challenges can result. Yes, you can use native SQL tools to manage both tablespace and user creation and allocation.  It may be wise to review the ArcGIS documentation on minimum permissions, or to use the Create Database User tool at least once to make sure you've met the requirements for a data owner account, but once you've identified what is necessary, creating new users wouldn't require much work. Don't forget that you can allocate more storage to tablespaces, up to the limits dictated by block size, BIGFILE/SMALLFILE property, and disk allocation on the device to which the datafile is allocated.  If you have overfilled a tablespace, creating a new one won't alter the allocation of existing tables; you will likely need to transfer or recreate the table(s) in the new tablespace, which can cause "high water mark" issues on the previous tablespace.  Untangling the nested issues may take a detailed implementation plan. Good luck! - V ... View more

8Gb RAM for 56 services isn't all that much, considering Windows consumes 3Gb for just the OS (it works out to just  45.7Mb per instance with two instances per service).  "Server class" processing hosts should have at least 16Gb RAM (my last database server purchase had 256Gb RAM). The next home PC I buy will have 16Gb RAM, so I'm due to review RAM pricing to see if 24Gb or 32Gb is the next "server" minimum.  If your server can't afford to have all services at their maximum instance count without exhausting RAM, then some research is needed into access frequency to review proper instance maximums and RAM requirement. The drawback to dropping the minimum services to zero is increased latency for initial service access.  It's great for infrequently accessed services (alternate basemaps and the like), but it may impact service time for services which are being accessed at an interval slightly larger than the maximum idle time (and CPU system load from the added shutdown/startup effort for those services). - V ... View more

You could also use Kernel Density (requires Spatial Analyst) to make a heatmap, then Reclassify (also SA) and convert Raster to Polygon​.  This would give you a series of concentric rings indicating frequency of observations.  It takes a bit to fiddle with the parameters, but this is a very powerful visualization tool. - V ... View more

I was able to confirm that this can be done, using the Dissolve tool.  The Multipart To Singlepart​ tool can convert multipart features (e.g. Hawaii) into individual features without losing geometry (the attributes are repeated for each part). Passing file geodatabase rows through Excel and into an event theme is a long way around the block as a replacement for a simple two cursor copy (Query/Insert), and it's not obvious how you would make a multipoint geometry from such a solution.  - V ... View more

I try to spell out "Longitude" and "Latitude", or use 3-character abbreviations (which won't collide with a datatype reserved word in any platform).  Where possible, I try to include units as a postfix or prefix (e.g., "LatitudeDD", "DMS_Lon",...).  Using "Long" causes me to break out in hives (same as with spaces in directories).  I suppose "LonX" and "LatY" wouldn't require benedryl, but it might be a close thing. - V ... View more

It is for new features that I will create within the same feature class that I want to have the option of having either 1 or several points. Unfortunately, this is not possible.  Some storage formats (you didn't say which one you are using)  implement this differently than others, but you really will need to copy the existing feature class to a degenerate multipoint feature class.  Note that the storage may be significantly larger (e.g. ~2.3x in the .shp of a shapefile - from 28 to 64 bytes per feature) and the spatial index for multipoints is much less efficient than for points, so if there are a large number of features (100k+), you will see measurably slower spatial query performance with single-part MPOINT features in a MPOINT layer (vice POINT data in a POINT layer). - V ... View more

All Esri products come with local documentation.  The updates (most of which are fairly subtle) are bundled into successive releases.  In my view, the fact that Internet connectivity gives access to these updates without continual local updates is a benefit, not a drawback.  Making local documentation portable to a vast array of potential alternate viewers, when those viewer platforms aren't capable of executing the software seems like a distraction from the goal of improving the software and documentation.  There are issues with assumed connectivity in the Esri platform, but I'm not convinced this is a major one. - V ... View more

For reference, there was a long discussion on this topic over in GeoNet: https://community.esri.com/thread/169321 A warning before clobbering an older format file would be nice, but then there needs to be a mechanism to defeat this feature (when folks are intending to clobber, and don't want to hit dozens (or hundreds) of "Ok" buttons).  A user interface to set the default save-as release version would be much more work. ... View more

For the record, Point feature classes are "npc" Multipoint feature classes are "npc+", Polyline feature classes are "nlsc+", and Polygon feature classes are "nac+" 3-D (well, 2.5-D -- X/Y with Z) would add "3" and measured shapes add "M" (any order). Geodatabase annotation isn't a separate topology class in enterprise geodatabases; I wouldn't recommend using the deprecated command-line tools to interact with them. The documentation can be found in many places, including here​. - V ... View more

I understand the reluctance to go to Tech Support without your problem quantified (I just spent a month getting an ArcObjects Java bug entered), but waiting days/weeks to get into the queue won't make your experience faster. Far better to start the process, with the hope that it's a known issue, than to burn more time trying to come up with a solution, then start the clock ticking.  Even though some Esri folks are active here in GeoNet, many are not, and this is a user interaction framework (with likely the same, or worse, interaction ratio). If you're not getting what you need from local Tech Support, you have at least two better mechanisms: Talk with your marketing rep to help grease the skids (they'd need to be on board to get a QFE build for a non-terminal ArcGIS release anyway) Talk with Esri corporate HQ in Redlands There really isn't much anyone here can do with this class of problem, so placing GeoNet on your critical path to resolution isn't likely to improve your Support experience. - V ... View more

These sort of repeating non-reproducible issues should really be tackled in a Tech Support incident.  Often a snapshot of the database is required to unravel what is wrong. - V ... View more