Latest Contributions by JoshuaBixby

Version differences tend to have the biggest impacts on Web tool compatibility—ArcGIS Pro | Documentation and Geoprocessing services compatibility—ArcGIS Pro | Documentation.  ArcGIS Pro and ArcGIS Enterprise compatibility Although you can publish a service from ArcGIS Pro to earlier and later versions of ArcGIS Enterprise, using the equivalent version is recommended. If you do not have the equivalent version of ArcGIS Enterprise, publishing to a version that exceeds a minor version difference of more than two is not recommended. So, ideally, Pro and ArcGIS Enterprise are running the same/equivalent version, but it is common for the desktop client to get a bit ahead of the server applications.  The further apart the versions, the more likely there will be issues.  For our organization with tens of thousands of GIS users, we let Pro go ahead by a minor version since upgrading ArcGIS Enterprise every 6-8 months is a tall order. ... View more

I think a big reason that 1,000 was picked specifically, instead of 500, 2000, or some other number, is that Oracle historically limited the number of expressions in a single IN condition to 1,000.  From IN Condition: You can specify up to 1000 expressions in expression_list. Oracle did raise that number to 65,535 with Release 23, but Esri still supports older versions.  So the 1,000 number is a lowest common denominator approach that will work across a range of database systems and not require a special one-off syntax just for Oracle. ... View more

Regarding @LyonMNGIS wrote: ... I would expect any null records to show up on the map because they are not equal to hidden.  Am I missing something? ... The existence or possibility of NULL means SQL operators implement three-valued or ternary logic.   Instead of the true/false outcomes of boolean logic, there are true/false/unknown outcomes.  If you write: check <> 'Hidden' The records that are NULL return unknown, not true or false.  Since the result is unknown, the database will not return them because it is possible they could be 'Hidden', and it only returns records that are guaranteed not to be 'Hidden'. There are people who strongly oppose allowing or using NULL in any data model, including CJ Date who is credited with creating the relational model that SQL databases partially implement. I will note that prior to ArcGIS Pro 3.3, Esri's implementation of three-valued logic with certain operators in the file geodatabase was inconsistent with SQL standards and the rest of the industry.  Esri fixed the issue to be consistent with everyone else at Pro 3.3, but it also means certain queries can produce different results between Pro 3.2 and earlier and Pro 3.3 and later. ... View more

Short answer, you can't.  Typically software companies document requirements, not non-requirements because listing the latter would be a never ending task.  That said, sometimes a specific non-requirement is important enough to state clearly. In the case of feature services (see Feature services—ArcGIS Server | Documentation for ArcGIS Enterprise), there are a lot of requirements so it can be easy to get lost going through them all.  Probably the most concise statement that answers your question, albeit it doesn't necessarily jump off the page, is from Prepare data to publish a feature service—ArcGIS Server | Documentation for ArcGIS Enterprise: Requirements common to geodatabases and databases The following requirements are true whether the source data is stored in a relational database, a cloud data warehouse, or an enterprise geodatabase: The 3 types of "databases" mentioned are relational, cloud data, and enterprise.  A file geodatabase is not included, nor is a mobile geodatabase, shape files, or many other data formats. ... View more