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.
Updated links to ideas:
A lot of improvements on the geodatabase side have been made in the lastest ArcGIS releases like renaming and modifying columns and making the sde command line tools available via tools. The possibility of creating proper spatial views however, still needs attention before deprecating the current tools.
'sdemon' certainly did require SDE user access rights, it just passed those access
rights to any connection on the port (which could be construed as a security hole).
- V
We specifically use the sde command-line scripting to handle loading data into sde from non-Windows platforms such as Linux systems. All in all this move away from sde command line is not very helpful for those of us that are just trying to automate loading of shapefiles into SDE/geodatabase in a shell scripting environment on a Linux platform.
# Name: FeatureClassToGeodatabase_Example2.py # Description: Use FeatureClassToGeodatabase to copy feature classes # to geodatabase format # Import system modules import arcpy from arcpy import env # Set environment settings env.workspace = "C:/data" # Set local variables inFeatures = ["climate.shp", "majorrds.shp"] outLocation = "C:/output/output.gdb" # Execute TableToGeodatabase arcpy.FeatureClassToGeodatabase_conversion(inFeatures, outLocation)
# Import system modules import arcpy from arcpy import env # Process: Create Database Connection File... # Usage: out_file_location, out_file_name, DBMS_TYPE, instance, database, account_authentication, username, password, save_username_password(must be true) arcpy.CreateDatabaseConnection_management("/net/shared/location/connections/", "zion.sde", "ORACLE", "zionserver/ORCL") # Set environment settings # Set the workspace to the specified data location env.workspace = "/net/sharedata/location/data" outLocation = "Database Connections\zion.sde" # Get all the feature classes in the environment # list of fc's should be similar to this: ["accident.shp", "veg.shp"] inFeatures = arcpy.ListFeatureClasses() # Process: Load Data (Use the "Feature Class To Geodatabase" Tool...) try: # Execute FeatureClassToGeodatabase print "Loading data...\n" arcpy.FeatureClassToGeodatabase_conversion(inFeatures, outLocation) except: for i in range(arcpy.GetMessageCount()): arcpy.AddReturnMessage(i)
Examples: (Linux) /tmp>loaddata_sde_params.py --DBMS ORACLE -i myserver/orcl -u user1 -p user1 --dataloc /net/sharedata/location/data (Windows) c:\tmp>loaddata_sde_params.py --DBMS ORACLE -i myserver/orcl -u user1 -p user1 --dataloc \\sharedata\location\data >loaddata_sde_params.py --help Usage: loaddata_sde_params.py [Options] Options: --version show program's version number and exit -h, --help show this help message and exit --DBMS=DATABASE_TYPE Type of enterprise DBMS: SQLSERVER, ORACLE, or POSTGRESQL. -i INSTANCE DBMS instance name --auth=ACCOUNT_AUTHENTICATION Authentication type options (case-sensitive): DATABASE_AUTH, OPERATING_SYSTEM_AUTH. Default=DATABASE_AUTH -u USER user name -p PASSWORD password --dataloc=DATALOCATION Path to the data (either a geodatabase or a directory with shapefiles -D DATABASE Database name (Not required for Oracle)