Latest Contributions by TanuHoque

Joe Borgione wrote: At 10.1 and later versions, edits made to the source data (such as feature classes displayed in a map) should be immediately visible in the service as long as a copy of the data was not placed on the server when publishing Joe, lets see whether I can explain it clearly. Unlike pre-10.1 server, starting at 10.1 (put that in very simple way), you can publish a service (a) by referencing the original data and (b) by copying data on the server along. As you may have noticed that the publishing process is different at 10.1 and depending on your workflow (which seems like the case for you) you may want to 'register' the FileGDB / SDE/ folders etc. (that layers in your mxd pointing to) to the 'data store'. If you don't do that you will see an analyzer warning and if you accept, your data get copied to the server; and the service starts to use that version of data (off a server's managed location) instead of the workspace layers in your source mxd referring to. Option (a): this is like pre-10.1 server. you create a map document in ArcMap, you add bunch of layers e.g. from a FileGDB, you register the workspace and you publish... in this scenario, as you update you data in the workspace, every map refresh or query operation call will give you the updated data. No service restart, no overwrite needed. Option (b): this is when you do not register the workspace to the data-store and right before publishing process starts, you accept to copy data on the server. In this case, layers in that map/feature service will *no* longer refer to the workspace that the layers in the source mxd refer to... instead they refer to a managed workspace on the server... In this particular scenario, if you data get updated, yes, you need to overwrite the map/feature service so that the data on server get updated as well. Hope this help. Sorry about the lengthy reply. ... View more

In ArcCatalog or ArcMap's Catalog window, you can right click on a map service and select 'Service Workspaces...' which will bring up a dialog to all workspaces referenced in the mxd In Manager (may not be available in 10.1x), there is a database icon next to each service name, click on it to view all database referenced by the service. hope this helps ... View more

Hani, Unfortunately this is known limit when you have StandardardizedQueries enabled. If you data are not sensitive, then you may consider disabling StandardizedQueries or copy values from Shape.STArea() field to a separate field and query on that new field -- these are workarounds I can think of. ... View more

Enguerrand, As you know a Feature Dataset is just a logical group containing FeatureClasses etc. The name of the FeatureDataset a FeatureClass 'logically' lives in, is NOT a part of that FeatureClass's name. Therefore, in your case, simply removing the FeatureDataset name from dataSrourceName should make it work. If you really need to (sometime you probably have to) fully qualify the FeatureClass name in 'dataSoureName', then you do it the way it appears in ArcCatalog or ArcMap Catalog Window. Hope this helps. Tanu ... View more