Latest Contributions by VinceAngelo

Please post Python questions with the code in the question as text (formatted in a code block) -- It allows others to try your code without retyping it from scratch.  If you need to redact pieces, be sure to explain what they were sufficiently so that suitable scaffolding can be applied. - V ... View more

I'm a "big iron" guy, so I haven't used Access, but a quick set of searches indicates that OLEDB doesn't support LOBs from real databases like Oracle, and maps Memo to wide string (DBTYPE_WSTR)​, so it doesn't appear that Esri has much control over how to access memo fields through that kind of connection. - V ... View more

If the OLE provider marks the source as a "String" rather than a "CLOB", it's possible that ArcGIS will place a string limit on the field length (or that the limit is imposed before ArcGIS sees the field).  OLE dates back to the days when dBase ruled the "database" world, so it's not impossible that the 256 limit is part of the protocol (and that no CLOB exists). I fear you will likely need to pursue the split/reassemble approach, though as long as your data does not contain multi-byte UTF8 sequences, splitting on meaningful boundaries probably would not be required. - V ... View more

To some extent, that may differ by the release (or even patch level) of the installed geodatabase, as well as the RDBMS in use.  What release and RDBMS are you using?  Has something unfortunate happend to your geodatabase instance? - V ... View more

As George writes, the restriction for owner in user-schema geodatabases is a design characteristic. The default tablespace isn't a problem so much as a property that needs to be managed.  If you set the default tablespace for the user where you want USER data to go, then use the Tablespace Name option on the user-schema geodatabase creation tool, tables will go where they belong. - V ... View more

I strongly discourage creation of user-schema geodatabases because they don't provide the isolation that they purport to. Case in point:  You should not create user-schema geodatabase tables in the SDE user's tablespace (doing so will likely overtop the SDE tablespace).  You should also not ever create user tables in the tablespace where either SDE or the user-schema geodatabase tables reside (the one client that convinced me it was necessary had three-plus tablespaces -- SDE, USERGDB, USERDATA1,...) - V ... View more

This isn't an apples-to-apples comparison, and application bit size doesn't really have any bearing. ArcGIS Server is a 64-bit application, but there are a number of factors that come into play: The geoprocessing job needs to be queued, then taken off the queue There may not be a started service available The scratch workspace associated with the job needs to be created The CPU class of the server is likely different from the desktop The disk characteristics on the server is likely different from the desktop You can add Verbose level logging to your app to break out the timing of the elements of the job, but logging can increase runtime, so that can be a two-edged sword. - V ... View more

You should also mention that this question was asked in gis.stackexchange​ (twice, in fact), but was deemed unclear.  It would probably help if you provide more information, including the version of ArcGIS in use, the contents of the directories, and, after adding a lot more diagnostics, the output of the script with those diagnostics.  It's very difficult to help based on the information provided. - V ... View more

The most relevant question in all "All of a sudden, it's not working" situations is "What has changed?" Unfortunately, with the modern division of IT, DBA, and geodatabase admin, the answer may not be all that obvious.  Then there's the counter-example -- I once had a mail server stop working when I changed the domainname, and eventually it was tracked down to the SunOS4 box being up for over 2 billion (2^31) milliseconds without reboot, and the OS bug just happened to occur while I was dorking with the system. - V ... View more

Since you're using a Microsoft geometry type, the Microsoft documentation is the place to locate SQL functions.  The other side of this is the "for a feature class in enterprise GDB".  I would urge you NOT to place such a function in a view -- the performance will likely be inadequate.  You'll need to weigh your "dynamically" constraint against performance. - V ... View more

Please clarify your question by specifying which RDBMS you are using (including a specific version) and which version of ArcGIS is available. - V ... View more

The DLLs are also available in the ArcGIS for Desktop install (as stated by the documentation).  Since you need to have either the Desktop or Server geoprocessing tool to enable a geodatabase, it makes sense to make the DLLs available in both (organizing and maintaining DLL distribution without the utilities needed to make them work makes less sense). - V ... View more

It's a bit more complicated than just a sequence, because sequence generation is too slow for bulk insert processes.  Instead, the sequence has an interval (size dependent on version) for a gap in values and a pipe is used to store the next value when a cursor is shut down.  When the next cursor comes along, it will fetch off the pipe before consulting the sequence, to prevent a gap.  If you shut down the instance, the DBMS_PIPE objects are lost, resulting in a gap in subsequent inserts (though there is a [somewhat elderly] KB document that addresses a workaround). - V ... View more

Connecting as any administrative user (SYS/SYSDBA/root/sa/postgres/...) for other than adminstrative use is an antipattern.  Doing so puts your entire database instance at risk from one wrong click.  "Worst practice" doesn't capture the risk adequately. Please do not do this!  Instead, use that administrative user to create the needed tablespaces, users, and roles, then put the password on an index card in a  locked filing cabinet and forget it. - V ... View more

You should not EVER use the SYS user to connect from ArcGIS clients.  It is a very dangerous practice, and Oracle tries to prevent it by making SYS-privilege users add the WITH SYSDBA modifier in the connection (which ArcGIS doesn't provide). If you follow best practice by creating one or more tablespaces to contain your data, and one or more users to own the data (with appropriate default tablespaces), and one or more roles to manage access to your tables, and additional users to access the data (through the roles), then you won't get tangled in knots trying to use administrative accounts for non-administrative purposes. - V ... View more