Latest Contributions by KimPeter

ArcGIS does not quote object names when it passes them to the database. If the object requires quotes for the database to understand, it will not work. See technical article 40571: http://support.esri.com/en/knowledgebase/techarticles/detail/40571. ... View more

Spatial Data Server is only available with ArcGIS Server Enterprise and will not work with workgroup geodatabases. One of the main reasons for using Spatial Data Server is to publish feature services from a database, though.  You can use ArcGIS Server Workgroup to publish feature services from workgroup geodatabases...  Or did you mean you want to use Spatial Data Server with databases in a SQL Server Express instance (not a "database server" that contains geodatabases)?  If so, you should be able to do that, as long as you have purchased ArcGIS Server Enterprise, which, as mentioned, is the only way to get Spatial Data Server. ... View more

Hi, As you mention, you can connect to, query, and analyze data in a database from ArcMap.  However, you cannot edit features in a database (any database; not specific to PostGIS-enabled PostgreSQL) from ArcMap. For that, you would need to create a geodatabase in your database and register the data with the geodatabase. ... View more

One slight clarification: It is the version of the client that is important. Datasets with 10.1 functionality, such as editor tracking or network datasets that support live traffic data, can be created in both 10 and 10.1 geodatabases but ONLY with a 10.1 client. Your 10 clients cannot create these nor can they use that functionality. I'm not clear how you were able to tell the version of your enterprise geodatabase but not your workgroup geodatabase...the enterprise geodatabase version is not exposed through the UI either.  Unless you mean you are using an ArcSDE service for your enterprise geodatabase and are going by the version of the ArcSDE application server you have installed(?) ... View more

Jon, Did you run the authorization portion of the setup wizard for ArcSDE for SQL Server, specifying an ArcGIS Server Workgroup license?  You shouldn't have to edit the registry directly. ... View more

As indicated in the What's new for geodatabases topic: "The recommended method to access enterprise geodatabases is to connect directly from ArcGIS clients. If you only use direct connections to your geodatabase, you do not have to install the ArcSDE application server." http://resources.arcgis.com/en/help/main/10.1/index.html#/What_s_new_for_geodatabases/016w00000031000000/ If you need to edit settings in the ArcSDE system tables, though, you should still install the command line tools included with the application server.  I don't think editing system tables directly through SQL is supported technically. ... View more

This is also documented in the setup topic for geodatabases in PostgreSQL: http://resources.arcgis.com/en/help/main/10.1/#/Setting_up_a_geodatabase_in_PostgreSQL/002p00000001000000/ In step 3 for Linux: Set the LD_LIBRARY_PATH variable to the PostgreSQL lib directory. The location of the lib directory can vary depending on how you installed PostgreSQL. To determine the correct location for your PostgreSQL installation, execute pg_config as the postgres user. Set LD_LIBRARY_PATH to the value that is returned for PKGLIBDIR. In step 7 for Linux: Move the file from this location on the ArcGIS client, log in to the PostgreSQL server as the root user, and place the st_geometry.so file in the PostgreSQL lib directory. (This is the same location to which you set the LD_LIBRARY_PATH environment variable.) ... View more

Are you sure the geodatabase was updated to be a Workgroup geodatabase?  You should never see a max connections message with a workgroup geodatabase.  Based on this: When I right-click at the Database Server Connection in Catalog>Properties we see "Class: ArcSDE Personal Server". ...it doesn't sound like you have a workgroup geodatabase.  Be sure to authorize the instance with a Server Workgroup license, then update the geodatabases as described in the topic on changing license keys that I referenced in April. Publishing services from a Desktop database server (ArcSDE Personal Server) is not supported. -Kim ... View more

Hi Carmen, When connecting directly from an ArcGIS client application to the DBMS (which you always do for workgroup geodatabases), the version of the geodatabase is determined by the version of the client you used to create or upgrade it.  That means that if you have mixed client versions, you could have mixed versions of geodatabases on the same database server. But when I view the properties from ArcCatalog 10.0 - the Upgrade status says "This 10.0 database matches the ArcGIS release you are currently using". Why would it say this? Is the full message "This geodatabase matches the ArcGIS release you are currently using, however, database internals such as stored procedures can be upgraded.", with an active Upgrade Geodatabase button?  Or is the Upgrade Geodatabase button inactive in all cases? Database Server properties reported in Catalog: ArcSDE Workgroup Server 10.50.1600.1 (would have thought it should say 10.1?) That's the SQL Server version, not the ArcGIS version. -Kim ... View more

Yeah, that command is active on the database context menu, which has confused people.  However, having the software do the check when you open the menu would be expensive performance-wise.  So the tool just fails when you pass it the Workgroup license instead.  Since opening the context menu is done far more frequently than running the Enable tool, we figured we'd go for the better menu performance. Everything's a trade-off. 🙂 ... View more

Rob indicated that he is using Workgroup geodatabases. The Enable Enterprise Geodatabase tool does not work to create a workgroup geodatabase. The way to create a workgroup geodatabase is to right-click the database server and click Create Geodatabase, as Rob did originally.  However, I'm not sure what caused the error message received, "Error creating this geodatabase. User, group, or role 'dbo' already exists in the current database.", and why geodatabase creation failed. Rob, you indicated you re-installed SQL Server Express using the executable provided with ArcGIS Server Workgroup and all is working now, right?  Perhaps the SQL Server Express instance you had before was not a version supported for ArcGIS 10.1(?)  For example, maybe it was 2005?  Or it wasn't SQL Server Express with Advanced Services? ... View more

The message you saw when trying to create the geodatabase was due to the fact that the ST_Geometry libraries had not been copied to the PostgreSQL server. The information about copying the ST_Geometry library is in several places in the documentation on the Resource Center: http://resources.arcgis.com/en/help/main/10.1/#/Setting_up_a_geodatabase_in_PostgreSQL/002p00000001000000/ "Move the st_geometry.so library to the PostgreSQL installation directory. The st_geometry.so library for PostgreSQL 9.0 can be found in the DatabaseSupport/PostgreSQL/Linux64 directory of your ArcGIS client installation directory. Move the file from this location on the ArcGIS client, log in to the PostgreSQL server as the root user, and place the st_geometry.so file in the PostgreSQL lib directory. (This is the same location to which you set the LD_LIBRARY_PATH environment variable.)" "Copy the st_geometry library to the PostgreSQL installation directory. The st_geometry.dll file for use with PostgreSQL 9.0 can be found in the DatabaseSupport directory of your ArcGIS client installation directory. Move the st_geometry.dll file from the ArcGIS client to the PostgreSQL lib directory on your PostgreSQL server." http://resources.arcgis.com/en/help/main/10.1/#/Tutorial_Getting_started_with_geodatabases_in_PostgreSQL/002p000000t4000000/ "Place the ST_Geometry libraries in the PostgreSQL lib directory Geodatabase creation in PostgreSQL relies on the presence of the ST_Geometry library. You must place the appropriate library in the lib directory where PostgreSQL is installed before you can create a geodatabase. ST_Geometry libraries can be found in the DatabaseSupport folder of your ArcGIS client installation." http://resources.arcgis.com/en/help/main/10.1/#/Creating_a_database_and_geodatabase_in_PostgreSQL/002p000000ss000000/ "At a minimum, you must install PostgreSQL and set it up to accept remote connections, place the ST_Geometry library on the PostgreSQL server, and install the PostgreSQL client on the ArcGIS for Desktop client machine before you run the Create Enterprise Geodatabase tool" http://resources.arcgis.com/en/help/main/10.1/#/Enabling_geodatabase_functionality_in_an_existing_PostgreSQL_database/002p000000sv000000/ "Copy the st_geometry library to the PostgreSQL installation directory. The st_geometry library can be found in the DatabaseSupport directory of your ArcGIS client installation directory. Move the file from the client to the PostgreSQL lib directory on your PostgreSQL server. If PostgreSQL is installed on Linux, log in to the Linux server as the root user and place the st_geometry.so file in the /usr/lib64/pgsql directory. If PostgreSQL is installed on Windows, place the st_geometry.dll fiile in the %PostgreSQL%\lib directory." ... View more

Hi Meg, As indicated, the date data type isn't supported at 10.1 either, so upgrading will not change that. http://resources.arcgis.com/en/help/main/10.1/#/SQL_Server_data_types_supported_in_ArcGIS/002q00000068000000/ I'm not sure why datetime would not have worked, though.  Fields of that data type should be visible in ArcGIS. ... View more

You can't edit individual features from ArcGIS Desktop; currently for that, you'd need to publish an editable feature service to ArcGIS Spatial Data Server.  But you can create tables, alter schema, and load data from Desktop.  See this help topic for an overview of functionality available when connecting from ArcGIS Desktop to a database: http://resources.arcgis.com/en/help/main/10.1/index.html#/A_quick_tour_of_working_with_databases_in_ArcGIS/019v00000008000000/ ... View more

I did some research and found that the problem is that the feature service source must be in the database (or geodatabase).  The XY event layer isn't a table in the database, it is a layer in ArcMap.  When publishing, the spatial data server is looking for the event layer in the database, but it doesn't exist. You could publish the XY event layer as a map service to ArcGIS Server.  But since Spatial Data Server only uses feature services, what you are attempting to do is not possible. ... View more