Latest Contributions by RussellBrennan

This should do the trick: import arcpy  arcpy.env.workspace = r'Database Connections\Test.sde'  dataList = arcpy.ListTables() + arcpy.ListFeatureClasses() + arcpy.ListRasters() + arcpy.ListDatasets("", "Feature")  for dataset in dataList:   desc = arcpy.Describe(dataset)   if desc.isVersioned:     print desc.name ... View more

Alan, To further add on to what Jake said... Prior to 10.1 (10.0, 9.x, 8.x) if you wanted to use a Geodatabase with all of the cool Geodatabase functionality (versioning, archiving, topology, relationship classes, terrains, geometric networks, etc) on a DBMS (Oracle, SQL Server, Postgresql, Informix, DB2) you had to perform a few steps. First, you needed to install ArcSDE onto your machine, usually this was your DBMS server. This install included the files needed to run ArcSDE command line utilities, the application server, as well as the ArcSDE post installer. After installing this onto your machine you would need to run the ArcSDE post installer. The main purpose of this post install was to install the Geodatabase into your enterprise database. This includes all the stored procedures, functions, privileges, and schema needed to provide the functionality I mentioned earlier. The post install could also be used to set up your application server. The application server can be used to connect from a client machine to the DBMS/Geodatabase. It is used more or less to manage the connection requests coming in from clients and provide a way for the clients to 'talk' to the DBMS. For a while this was the only way to connect to a Geodatabase. At some point (I think 9.0) we added the ability to make direct connections (2-tier: client-DBMS) to the DBMS. This made the use of the application server (3-tier: client-app server-dbms) optional. For some people this meant they stopped setting up the application server and started using direct connections. Others continued using the application server. The ArcSDE command line utilities are a method for the Geodatabase administrator to manage data, users, the application server service. Fast forward to 10.1 - We have tried to allow you to manage your Geodatabase completely within ArcGIS applications (ArcCatalog, ArcMap, ArcGIS Server, etc). This is done through the use of dialogues in ArcMap/Catalog and the use of geoprocessing. The first thing we did was to break out the installation of the geodatabase schema tasks into geoprocessing tools. If you want to create an enterprise geodatabase there are now two options. Option 1, you can use the 'Create Enterprise Geodatabase' geoprocessing tool. This tool will create a new empty geodatabase in an existing instance. The second option is to use the 'Enable Enterprise Geodatabase' tool will allow you to install the Geodatabase schema in an already existing instance. The new functionality that Jake mentioned that allows you to now connect to a enterprise database (not a geodatabase) is what allow ArcGIS to then enable geodatabase behavior in your enterprise geodatabase. This second option would be used where you have already set up a database, have user permissions assigned and maybe have loaded some data (essentially converting your database to a geodatabase). The first option would be used if you are starting from nothing. Esri recommends using direct connections for making connections to your geodatabase, it is not mandatory that you install the application server. Much of the commonly used functionality found in the ArcSDE command line utilities is now available either through ArcGIS applications mentioned earlier or through geoprocessing (disconnecting users, identifying locks, loading data, investigating data, etc). For most users the install of these utilities should not be necessary. If you determine that you really need the application server or the command line utilities they are available as a separate install. So, this has been a pretty long winded answer to a pretty straightforward question. Answer is, it's not mandatory to install the application server or command line utilities. If you want to take advantage of Geodatabase behavior you do need to run one of the geoprocessing tools to install the Geodatabase. ... View more

The following code should help. I put in an excessive amount of comments to make this clear as I don't know your skill level with Python. import arcpy  #Create a table in memory to hold the codes and their descriptions for a particular domain. cvdTable = arcpy.DomainToTable_management(r'C:\vancouver.gdb', 'type', 'in_memory/cvdTable', 'codeField', 'descriptionField')  #Create an empty dictionary. d = {}  #Create a cursor to loop through the table holding the domain and code info rows = arcpy.SearchCursor(cvdTable)  # Loop through each row in the table. for row in rows:   # For each row in the table populate the key with the code field and the value from the description field   d[row.codeField] = row.descriptionField #Cleanup del row del rows  # Create a search cursor on the table with the domain rows2 = arcpy.SearchCursor(r'C:\vancouver.gdb\TESTFC') # Loop through the records in the table. for row2 in rows2:   # Print the dictionary value for each code that is returned from this search cursor   print d[row2.PipeType] #Cleanup del row del rows Hope this helps. ... View more