Latest Contributions by NateArnold

Vince Angelo‌ Now that 10.3 Pre-release is out, can you clarify what the better solution is? ... View more

I'll add to this thread that in May of 2013, I submitted an incident which got tagged onto NIM085579, which is currently listed as Open and Assigned.  This bug was created TWO YEARS AGO and it has still not been fixed.  The analysts found that yes, a view created with CreateDatabaseView_management against a feature class using geometry storage (which is the default now) in SQL Server 2012 is indeed slower than command line spatial views against feature classes using sdebinary storage.  The analyst I was working with at the time said (c/p from an email):           So the slower drawing time seen in the view created with SQL is expected.  Please let me know if you have any questions about this. Please, ESRI, don't be surprised when users like Joshua Bixby‌, me, and everyone else in this thread get frustrated on the subject of spatial views, when "it's slower now by design" is the type of response we get from Tech Support.  Add to that command line tools going away, and what are we to do???  Please, please, please share the suggested workflow for making spatial views at 10.2+.  And don't say saving a .lyr file is part of the solution. ... View more

Melissa Jarman‌ I do not believe that database views were intentionally allowed to register with the geodatabase. It seems that there is somewhat of a loop hole that allows for this if the view is created with the SDE commandline tools or registered with the commandline (sdelayer -o register) first and then register with geodatabase is available in the client UI. What!?!  This is the workflow that Vince Angelo‌ said, is it not?  I always define my views with SQL, then register with 'sdelayer -o register'... That's what I'm trying to do - define the view in SSMS (or using CreateDatabaseView_management - they both give the same error in the end), then register the view with the geodatabase.  Vince, if that's not what you meant, please elaborate because I don't understand.  What is your intention or need for the database view to be registered with the geodatabase? I want to create a view in the database for which (1) users do not have to get bothered by a prompt for unique ID field or SR, and (2) geodatabase metadata can be modified.  Both of these were true of spatial views created with ArcSDE command line - if the capability exists at 10.2.x then I'm not aware of it - please share!! The administration reference you are sharing states 'table' and not view. I did find a reference in the 10.0 help regarding registering views with the geodatabase. I pulled the quote from the admincmdref directly from the document that gets installed with the ArcSDE command line tools 10.2.2 installer at %installdir%\ArcSDE\Documentation\Admin_Cmd_Refs\Support_files\admincmdref.htm.  If this is indeed a loophole, then it's still there at the current release.  Look in Data management commands --> sdelayer: Yes, it does say 'table' in this documentation, but if using this command is not exactly what Vince Angelo said to do, then I'm terribly confused. ... View more

Vince, the admincmdref documentation for 'sdelayer -o register' states: You can use the Register with Geodatabase command from the context menu of the table or the Register with Geodatabase geoprocessing tool to register a spatial table with both ArcSDE and the geodatabase. I've got feature class A stored in SQL Server with geometry storage, and table B.  I created a view (ABView) in SSMS that joins the table to the feature class.  The view includes A.Shape.  I'm using Desktop 10.2.2 against SDE 10.2(.0).  First, the Register with Geodatabase context menu item is disabled for this view.  Second, when I run RetisterWithGeodatabase_management against ABView I receive: ERROR 001399: Views are not supported. The command line help documentation does not seem to be correct, at least for views created in SQL.  The bigger issue is that (like you suggested) I am able to use 'sdelayer -o register' to register the view with the geodatabase.  So how are you going to be able to register views at 10.3+?  Has the behavior for RetisterWithGeodatabase_management changed at 10.3? ... View more

We've encountered similar circumstances with complex objects like topologies and geometric networks.  Once a delete or rename fails, the only way to clear the layer out of the table registry is sdetable -o delete.  If the table is not found, you're prompted to continue to remove metadata about the table (which removes the entry from the sde table registry if possible):      If not for command line, how are we to remove orphaned table registry items?  Does Delete_management have a similar table registry removal function?  ... View more

Hi Melissa: Thank you for your response.  I hadn't used the schemalockingenabled configuration for services and will definitely look into it.  However, the comment made by Tom Weisenberger was that command line sde doesn't care about map service locks in order to drop a spatial index. Does RemoveSpatialIndex_management need an exclusive lock or can it proceed with clients using the target layer? ... View more

This is a great thread, but also very troubling.  The most recent info we have from ESRI is: We're deprecating command line at 10.2 Vince Angelo says to register a sql view you need 2 steps - create the view then register it with soon-to-be-deprecated command line Drop the spatial index first in order to equate command line load_only.  Oh, by the way, this won't work when map services have locks on the data. We might have the ability to import/export dbtune past 10.2 I have to say that ESRI has been most unhelpful in providing info on what's coming up at 10.3 - just look at the number of threads there are on this topic!!  Your users rely on the type of spatial views that command line provided, and there is no combination of GP tools that allow you to create an "sde-registered" view.  Anyone who says using query layers in place of spatial views is an option seriously needs to go through this dialog when adding 30+ views to an mxd - you'll understand our pain: It's a joke that ESRI marked this idea as "implemented":  ArcGIS Idea - Create SDE spatial view from ArcGIS Desktop Please ESRI let us know what you have upcoming for 10.3 so we can plan accordingly. ... View more

Your frustrations will grow when you go to publish a mosaic dataset using AGS, only to find that the Image extension is required. ... View more

+1 on this 🙂 Referencing data already on our web server would be great, since we're not using AGO for data hosting.  We already have our own open data catalog in place, but it lacks the multiple format download options of open data.  I'm actually working on a rolling 180 day crime export right now (csv with lat/long), and it would be great to upload this to our web server and have it published to open data.  I imagine for others direct upload of csv (with an associated tool/arcpy element) to hosted AGO would be useful, plus as you mentioned upload from ESRI Maps for Office. Nate ... View more

The 'sdelayer -o register' command is used to register tables or views in native storage (or ST_GEOMETRY, where available) with ArcSDE Thanks for that.  Bummer more command line. Nate ... View more

Also, one other problem we had when coming from 9.3 to 10.1 was that we changed from the default LONGRAW storage in Oracle to Geometry in SQL Server.  Changing data sources in our AGS mxd's to the new gdb resulted in problems with the shape area and length fields.  ArcMap did not properly interpret the change in fields, and the publisher/analyzer did not catch the problem, which resulted in AGS map service errors.  I'm not sure if any of the newer builds have caught this though.  Nate ... View more

They certainly can be registered with an enterprise geodatabase, if you a) have an enterprise geodatabase, and b) choose to do so. Please explain how to do this.  I've created a view using CreateDatabaseView_management, in a SQL Server gdb, using an owner account, on a feature class owned by that account.  After creating the view, right-click context menu --> Regsiter with geodatabase is greyed out.  When I run RegisterWithGeodatabase_management against it, I receive ERROR 001399: Views are not supported. Query Layers are a way of accessing spatial databases without ArcSDE.. This is an interesting point.  True, CreateDatabaseView_management can be used for non-spatial table views too, but if it's used against feature classes that are already in ArcSDE, I think the tooling should be able to take advantage of registering the view instead of leaving it as a query layer. It's not just spatial views, it's all tables which involve GEOMETRY/GEOGRAPHY objects, but these are an aspect of Microsoft's database implementation (and the difficulty of tuning it), not anything Esri has control over. That's fine, just as an FYI to the original poster.  We found for best performance with our data, load datasets into ArcSDE with the SDEBINARY keyword, then build the registered spatial view with command line tools.  Of course, you should try it with one of the other storage types and compare 🙂 Nate ... View more

Vince, From an end user perspective, I think ESRI has done a terrible job of clarifying differences between spatial views and query layers:  When you use SSMS to make a "view that includes a spatial column", why would it not be interpreted as a "spatial view" (confusion in terms)?  When the CreateDatabaseView_management tool was introduced, why would an end user not think "I can use this tool to make a spatial view", when it actually gets interpreted in ArcGIS as a query layer?  Why can views created using SSMS or CreateDatabaseView_management not be registered with the GDB (and hence store feature type, extents, description/metadata, etc.)? ArcGIS 10.1+ has seen much of the command line tools become GP/GUI tasks, but creating actual spatial views is one are where ESRI needs to focus.  Since there is indeed a speed difference between spatial views and query layers, but views are much easier to manage using SSMS, our approach has been to make a "dummy" spatial view using command line, then modify the view definition in SSMS.  We've also seen a speed difference between spatial views built on feature classes stored in the default Geometry spatial type (slower) versus SDEBINARY (faster).  Nate ... View more

Paul, Thanks for posting your solution - I needed pip and poster, which required setuptools.  Your workaround helped me get everything working. Nate ... View more