Latest Contributions by DavidHoy

Hi, By default, only the data owner can "see" the items in their schema - and that is reflected in the Catalog pane of ArcGIS Pro. but, this could happen if your users (or a role/group of which they are a member) had been granted access by the schema owner, or  have been granted db_datareader or db_datawriter system role. ... View more

sorry - That sounds correct, but I am not sure - and I don't have any sites set up at present to look for myself ... View more

Thanks for the tip Mick. Another trap we have discovered comes when using a Pro 3.3 VM to author processing templates that then get added to the MD functions. If you have not yet upgraded your AID servers to 11.3 , you may find you have newer version of components in your .rft that are not yet supported. We needed to deploy a VM with Pro 3.1 to create the .rft and apply it to the MD from that VM before creating the Service Definition.   ... View more

Actually Ryan - keeping the initial site administrator (ISA) credentials the same is "sort of" mentioned in the. help doc ArcGIS Enterprise backups—Portal for ArcGIS | Documentation for ArcGIS Enterprise Must this item or setting be identical across deployments when running the WebGISDR utility? Item or setting 10.4.x 10.5.x, 10.6 10.6.1 and later Version Yes Yes Yes Public portal URLs Yes Yes Yes Services URL for federated servers Yes Yes Yes Registered data stores other than ArcGIS Data Store Yes Yes Yes Account credentials for the ...webgisdr.properties file Yes Yes Yes Portal content directory storage type Yes Yes Yes I say "sort of" because if you do use the ISA in the webgisdr.properties file (and I think most people do when using webgisdr) then this is saying you must use the same ISA credentials in the target. Your explanation of WHY this is so, is definitely helpful. ... View more

If I understand you correctly - you tried to set the version as part of the view definition. That's not what I meant. Just create the new view in a SQL client (not using Pro GP tool) using something like:   CREATE VIEW new_view AS SELECT * FROM your_table_EV WHERE some_condition;   Once your new view is created, then use the set_version command before running a query against your view   ... View more

if you create a view that includes the _ev versioned view you don't define which version you are accessing in the view definition (as you say, without further action it will return records from the "DEFAULT" version) But, if you want to retrieve records from some other version, you need to run the  EXEC sde.set_current_version ' child_version' This will mean all queries (in that session) after you have run that set_current_version will retrieve from the version requested. That includes the SELECT statements on the versioned view that are part of your view definition So, your view of a view will do what I think you want, but you will need to set the version as an initial step in your SQL Script before you run SELECT statements against the "view of a view". ... View more

if you read that article carefully, you will see the example :   SELECT id, species, reporter FROM sightings_ev WHERE reporter = 'chuck';   the clue here is that the FROM clause is using the "Versioned View" that is already created in the geodatabase for any versioned class. SO, you don't need to create a view - it should be there already. It will be named <featureclassname>_ev If you want to use this _ev in your own view of a view - that should work (but won't be very fast and you won't be able to edit that view of a versioned view). ... View more

Hi Joshua, maybe you could consider creating a Materialized View (MV) in your SQL Server and register that as a feature class and use it in your map source? One potential problem with this approach may be that any update in your source tables may trigger a complete refresh of the entire MV and that would then result in a full upload to AGOL each time the MV was refreshed. ... View more

Hi Brian - the solution for your wish to decide where the data is stored is already there. If you choose to publish a Hosted Feature Service, then the data will be copied automatically tothe system managed Relational Data Store (as you have seen). If you wish to publish a non-Hosted Map Service (with Feature Access enabled) you have a couple of choices. check the "copy data" option in the "share" dialog this will force the source datasets to be copied to the selected ArcGIS Server site (in your case I think you only have a single ArcGIS acting as the Hosting Server role) This will make the system copy the source datasets to the arcgisserver\directories\arcgissystem\arcgisinput\<servicename>\extracted\p20 directory. This is not an generally an optimal practice - as the copied data does not get updated as your original source data changes. Register you Enterprise Geodatabase as a database type data store (See Manage registered data stores—ArcGIS Pro | Documentation) Since ArcGIS Enterprise 10.7.1 - when you register data store with ArcGIS Pro or via the Portal web page, the are created as items in your Portal - and you will see them in Server Manager, but not be able to a configure these from Server Manager. If you use Server Manager to register data store - they won't show as items in your Portal. Once you have a registered data store and your source data is in that location (it could be a fileshare or an Enterprise Geodatabase), if your Pro map sources the data from that location (and uses the same access details (common .sde connection file say), you can opt to "use Registered Location" when publishing a non-hosted map service. This will mean your data is not copied redundantly and the latest data will always be being served up by your service. another option, if you do want data to be copied to the Enterprise Geodatabase during publication - you could add a separate ArcGIS Server site, register the Geodatabase with that Server and configure that registered data store as the "managed database". This allows use of the "copy data" option while publishing to that Server, but the copied data will go to the managed database rather than to the Server's "arcgisinput" folder. See this post for further info: Solved: About managed database in Server - Esri Community ... View more

and Monitor will show what you configure it to retrieve from the available inputs ... View more