Latest Contributions by MelissaJarman

I am also not aware of a way to delete a versioned view without the commandline tools. I would recommend contacting support to voice this need with a reason that it is necessary to within certain workflows delete versioned views. You can also look on the Ideas portal or post an idea of your own. 33300 - Can a multiversioned view be deleted without leaving an entry in the table registry? Ideas Portal - Sign in to ideas.arcgis.com first and then go to the link below: Geodatabase Multiversion View creationg control, naming, and Visibility in future releases https://c.na9.visual.force.com/apex/ideaView?id=087E00000004SL1IAM Here is an enhancement that is a placeholder for specific parameters within the sdetable command that don't have UI solutions/replacements for. NIM096539 - SDETABLE: Create geoprocessing tools or arcpy functions for operations performed when using the 'sdetable' command. ... View more

I do not see any changes to the 10.2 System Requirements page as of yet, but for 10.3 prerelease the following link can be referenced as a guideline: Note: Use these system requirements as a guideline for planning purposes as they are subject to change before the final release of ArcGIS 10.3. Minimum supported database versions PostgreSQL 9.1.13 (64-bit) PostgreSQL 9.2.8 (64-bit) PostgreSQL 9.3.4 (64-bit) http://pro.arcgis.com/en/administering/system-requirements/database-requirements-postgresql.htm ... View more

Nate - Did you give the schemalockingenabled a try yet? I did a quick test and this worked for my services accessing data that I wanted to update the spatial index on. The documentation does not state that there is a requirement for an exclusive lock for the 'Remove Spatial Index' tool, but this is in lines with a schema change. This changing from the older commandline tools to be more restrictive would make sense that you would want to direct this to an administrative windows to avoid possible performance issues for users accessing those datasets. I am wondering if the error message was : 001166 : Spatial index could not be disabled. ArcGIS Help (10.2, 10.2.1, and 10.2.2)   - Rules for working with Schema locks ArcGIS Help (10.2, 10.2.1, and 10.2.2)  - Error 001166 ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Schemalockingenabled ... View more

Sorry for my delay in response. I agree that the remove spatial index tool does appear to need an exclusive lock from my testing. I do not know if the commandline tool removes existing connections - maybe did not check for shared locks  against the datasets before dropping the spatial index previously. Please try the schemalockingenabled parameter within your map service to see if this alleviates the issues you are experiencing when trying to update the spatial index, etc. ArcGIS Help (10.2, 10.2.1, and 10.2.2) ... View more

Andrew - I believe you need to login to the Ideas portal first and then use the URL - this will work. Here is the title of the Idea on the site that you can also search for. Add update license tool for enterprise geodatabase before it expires ... View more

Nate - Thanks for bringing these concerns to our attention based on your comments. 1 - The commandline tools are deprecated starting at 10.3 release 2 - If you have specific workflows that can only be done through the commandline then please submit a support ticket for these to be investigated. 3 - Have you tried the schemalockingenabled within the map service to see if this helps? I would try this and if not submit this to support so that they are aware the new workflow for setting a layer in load only mode is not comparable to the older commandline tools with the flexibility of data that is being served in a service. 4 - There is a tool for this at 10.3 'Export/Import geodatabase configuration keywords' For your comment about the database views prompting for the unique identifier field - there is an existing bug for this and we are aware of this issue. I would suggest that you contact support and ask to be added to this bug since there is only the workaround of using the commandline tools to create the view or saving out as a layer file. NIM085661 - ArcGIS does not set the first not-null field it finds as the unique identifier for a database view. ... View more

Yes – I also noticed that these values are not being updated on the external facing sites. We will work on getting these updated as soon as possible. Please post back next week with your testing results. Thanks Joshua ... View more

Joshua - All of the defects that were created that have workarounds closely linked to using command line tools are being reviewed to be resolved. This bug appears to be a duplicate of NIM096391 and has been included as a fix for the 10.3 release. We are looking at getting this verified and documented as a duplicate. ... View more

This is an area of concern that users have voiced - It is taken into consideration in the following enhancement. You may also try logging an Idea or promote the existing Ideas out there that are similar - eg: https://c.na9.visual.force.com/apex/ideaView?id=087E00000005AYZIA2 NIM095919 – SDESETUP: Create geoprocessing tools or arcpy functions for operations performed when using 'sdesetup' command ... View more

Jessica - There are plans to incorporate a user interface tool to export and import DBTUNE configuration files in the 10.3 release. 'Export/Import Geodatabase Configuration Keywords'. ... View more

Regarding the .sdx SDEexport files - Below is an enhancement for an equivalent arcpy function or tool that will will be considered for a future release. If you contact support services with a good example of why these export files perform more optimally than other data transfer methods (XML workspace documents, etc) we can take a look at these cases and append them to these enhancements for justification. We will need to have a good working example (clear steps to reproduce) of how the SDEEXPORT files are more efficient other methods of data transfer. NIM095122 - SDEEXPORT/SDEIMPORT: Create geoprocessing tools or arcpy functions for operations performed when using the 'sdeexport/sdeimport' commands. ... View more

Tom - Give the 'Remove Spatial Index' tool a try - this should replace the commandline version of the sdelayer -o load_only / normal_io mode. Within the current commandline administrators guide there is a statement about this tool with a globe indicating there is a recommended workflow within the user interface to try - eg: load_only_io Sets the input/output (I/O) mode of the layer to load-only, dropping the spatial index, and allowing only store and replace I/O operations <esri globe> You can use the Remove Spatial Index geoprocessing tool or a Python script to drop the spatial index, placing the layer or feature class in load only I/O mode instead of this operation. ... View more

This has been logged as a documentation enhancement as non-versioned archiving is supported on tables and sql spatial types such as SQL Server Geometry\ST_GEOMETRY\SDO_geometry but not older geometry types such as SDEBINARY\SDELOB: NIM102878 - The "Enabling archiving on nonversioned data" section of the link below doesn't highlight the unsupportability of SDEBNARY or SDELOB feature classes. http://resources.arcgis.com/en/help/main/10.2/index.html#/Enabling_archiving/003n000000rs000000/ ... View more

I private messaged you for a test case showing this behavior - Support Services would be very interested in seeing if the default calculation for the spatial index grids is not working as well as your manually entered values for the spatial index grid. sdelayer -o si_stats is indispensible for maintaining some feature classes, and no equivalent is available in desktop at the current version. The GDBT spatial index examination tool at 10.0 sort of works, but command line works better and faster. Today I had to use sdelayer -o si_stats to examine and redesign the spatial indexes for statewide parcels. Before change, took four minutes to draw at a reasonably large scale. After change, 6 seconds or less. The before-change spatial index was the one "estimated" automatically by ArcGIS desktop when the data were loaded. Take away this command line tool and our ability to provide well-performing data will be crippled. ... View more

There is an old blog on this topic with similar comments within - "This tool was intentionally designed to work with the layers that are in the table of contents (TOC) of a map document. That being said, you can still get the changes of layers which are currently “turned off” or “unchecked” in the TOC. With this in mind, it is possible to create a map doc of all the layers and have them all remain unchecked so you do not encounter the rendering cost." Road Ahead – Version Changes Viewer http://blogs.esri.com/esri/arcgis/2008/05/12/road-ahead-version-changes-viewer/ ... View more