Latest Contributions by MarcoBoeringa

HI All,  Please help me understand this for the personal ArcSDE.  For the previous item... No, you do not need to install an ArcSDE 10.1 application server to get full geodatabase functionality, including multi user/versioning/history. So can I still use a personal ArcSDE with Desktop without ArcGIS Server, say on a laptop?  If so, do I need to through through the same procedure for creating or enabling a enterprise geodatabase?  If, so how.  The create geodatabase requires an authorization code for ArcGIS Server. Thanks Brian Kaplan Brian, there is no "personal ArcSDE", there is just the ArcSDE DLL's that incorporate all the functionality to allow a Direct Connect connection on your local personal PC to a (remote) enterprise geodatabase, but that isn't a product called "personal ArcSDE". Additionally, if you want to create an enterprise geodatabase (so no file geodatabase), you will need an ArcGIS for Server commercial licence, as ArcSDE / ArcGIS for Server is a sale / non-free product of ESRI, and using an enterprise geodatabase requires this licence, even if you only start using it for testing purposes. That is why you are being asked for an authorization code. You may be able to get a temporary trial licence for free for testing purposes, IDK, but as soon as you start deploying it, you will surely need a true paid licence. For that, there are two possible licencing levels: "ArcGIS for Server Enterprise" and "ArcGIS for Server Workgroup", see this page: http://www.esri.com/software/arcgis/arcgisserver/features/enterprise-workgroup ... View more

Hi Jamal, Can't answer all of your questions at this moment, but I did notice in your PDF with screenshots, that you seem to be confusing tables, tablespaces and the fysical datafiles they are made up off. These are three different entities in Oracle. A table resides in a tablespace, multiple tables can be in one tablespace. A tablespace has one or more datafiles (fysical on disk) associated with it, that make up the true storage of the data. I recommend you to view the following Oracle links: Tablespaces and Datafiles http://docs.oracle.com/cd/A87860_01/doc/server.817/a76965/c03space.htm Managing Tablespaces http://docs.oracle.com/cd/B19306_01/server.102/b14231/tspaces.htm ... View more

Still curious to the answer of this question, no-one a clue? ... View more

the great news is I found some super resources as I tried to troubleshoot. If anyone is seeing similar difficulties you should check out: http://proceedings.esri.com/library/userconf/proc12/tech-workshops/tw_36.pdf For some reason, Adobe Reader refuses to open this link in Firefox and fails with an error. It can be opened in Internet Explorer. ... View more

OOps, I noticed that 9.2 was not supported (yet), so I have reconfigured my environment as follows: PostgreSQL 9.1.3 (64bit) + Post GIS 2.0 (64bit) Connecting using ArcGIS desktop 10.1 sp1 (32bit) I have recopied the .dlls from the new postgresql install directory. I am still getting the same error. any insight is greatly appreciated, Fiona Fiona, I think Vince already answered your question: The supported versions are 9.0.5 / 1.5.1.  PostgreSQL has a history of making non-trivial changes in minor patches, so it's never safe to assume .x support even if .+1 or .+2 works. - V Seems ESRI currently only really "supports" 9.0.5 / 1.5.1 as highest versions. Using any other version, especially taking into account Vince's further remarks about "non-trivial" changes in new minor releases, is a potential gamble. ... View more

It was already installed so I'm not sure.  How do I find that information?  There's nothing to indicate it as 64-bit in the Programs and Features list in Control Panel.  I am able to access another server running ArcGIS Server 10.1 without an issue, so I assume that the Microsoft SQL Server 2008 Native Client I have on my desktop is compatible with ArcGIS Desktop.  That could be a faulty assumption. You may try to use the "SQL Server" ODBC driver instead of the "SQL Server Native Client X.X" too, at least if Microsoft has documented it to be able to connect to your SQL Server version, otherwise it won't be of use. However, I can't find it now, but I think I saw a recent thread where someone reported solving his specific issues regarding driver issues by choosing the non-"Native Client" older driver. I also recommend you to have a look at this thread by myself, regarding a Windows 7 ODBC driver issue I had. I don't know if it is a general issue and if it is related to your issues, but it will at least help you find out if you run the 32- or 64-bit driver: http://forums.arcgis.com/threads/70820-BIG-TIP-for-ArcGIS-ODBC-OLEDB-users-on-64-bit-Windows ... View more

Many thanks Macro, I thought that there might be an indicator to show the name of the version and/or user in the table (to know where we are!) Best Jamal Agree, it can be convenient in some cases, although I remember seeing some discussion about IT security / privacy related issues with such an exposure of database user names from within the ArcGIS interface. After all, they are part of the database login. ... View more

To Jamal: I am working on a small PDF file with one figure / diagram that should clear up much of your, and other's, confusion around the "ESRI Geodatabase framework" (if I may call it so...) and all the components / applications involved. I hope to post it tomorrow in the "Why would I install ArcSDE with 10.1?" thread, as there is already a ton of good info by multiple contributors in that particular thread. Stay tuned. Marco ... View more

I�??m wondering why the version and its owner are not shown along with the name of the attribute table. In this case, what is the best practice to distinguish between them? The name of the table is directly derived from the layer name, so if you change the layer name manually to something appropriate upon adding it to the ArcMap TOC (Table Of Contents), you should see different names for tables. ... View more

I'm exploring sdetable -o create_view command making the view as a M:1 and including the shape field so there are geometries for all records.  This works well except views are not editable...is this correct?  Is there a way around this? One additional remark concerning the above statement in your first post: Creating a view should allow you to view the fields of both the base table and the related table in one "view/query" in a 1:M relationship. However, in a sense it is logical you can't "edit" such a view directly, as the view is de-normalized, and the records of the base table have been "virtually" duplicated for each related record in the base table. This older ArcGIS 9.3 Help page also states: "Spatial views contain a single spatial column. You can create spatial views in the same way you create other views; just be sure to include the geometry column in the view definition. The table containing the spatial column must be the same table that provides the row ID (also called the ObjectID) column for the view. Spatial views cannot be edited through an ArcSDE client." And this 10.0 Help page talks about multi-versioned views that can be edited, but only in certain specific situations, and not from within ArcGIS: "Multiversioned views incorporate database views, stored procedures, triggers, and functions to access or edit a specified version of a table or feature class in a geodatabase using SQL." This requires the Table or Feature Class to be versioned, just like the versioned editing of any enterprise geodatabase. And editing from within some custom webapplication or non-ArcGIS (e.g. AutoCAD) application. As that last Help page also states: "The primary use of multiversioned views is to edit versioned data using SQL. You cannot modify the underlying table or feature class through a multiversioned view using an ArcGIS client application." Also, multi-versioned views do not support relationships or joins, they can only be defined for a single Table or Feature Class, see below: "Multiversioned views only work with an individual versioned table or feature class. You cannot use a where clause to join multiple tables together or restrict which rows or columns are included in a multiversioned view." ... View more