|
POST
|
I meant support for SQL-Server's spatial types -- GEOMETRY and GEOGRAPHY columns. The combination itself is completely unsupported by Esri (9.1 is in "retired" status). - V
... View more
09-22-2011
09:15 AM
|
0
|
0
|
1303
|
|
POST
|
Robert brings up a great point. If you want your geodatabase to be portable, you should also strive to check your naming against *all* RDBMS keywords (most of which are SQL reserved words ["SELECT", "FROM",...], and many of which have overlap ["TABLESPACE"]). - V
... View more
09-22-2011
09:06 AM
|
0
|
0
|
5797
|
|
POST
|
SQL-Server 2008 support was not introduced until ArcSDE 9.3. There is little chance that this combination will work (see Vince's First Law of Compatibility), and no chance at all for spatial type support. - V
... View more
09-22-2011
04:28 AM
|
0
|
0
|
1303
|
|
POST
|
This is the same as any SQL restriction. First letter must be alpha. Remaining letters may be alpha-numeric or underscore. No spaces. No hyphens (which would be interpreted as "minus"). Keep in mind that these column names will be substituted for by row contents when the SQL algebra and calculus is applied, so math symbols and punctuation would make parsing the SQL expressions difficult, at best. While name length is limited to 64 characters, you should really expend effort in trying to keep column names inside 20 characters (ideally, 30 max), just to make your SQL readable. The only reason you should keep the name under 11 characters is if you intend to make shapefiles out them on a regular basis, but making sure the names differ in the first 10 characters will make your life easier. There is very little similarity between a column heading in a spreadsheet and a column name in a database (the same level of similarity between spreadsheets and databases, come to think of it). - V
... View more
09-22-2011
03:14 AM
|
0
|
0
|
5796
|
|
POST
|
Editing the SDE_* and GDB_* tables is very much not recommended (and almost never necessary). The supported mechanism for acknowledging new columns is to run 'sdetable -o describe' as the table owner. - V
... View more
09-21-2011
02:02 PM
|
0
|
0
|
1470
|
|
POST
|
There won't be a solution for this until 10.1 is released. - V
... View more
09-21-2011
04:22 AM
|
0
|
0
|
1335
|
|
POST
|
While it might seem like ArcSDE was okay with it, NUMBER is not a valid rowid column type, since it maps to SE_FLOAT64_TYPE. You can't remove entries in the column registry without risking your ArcSDE instance, but you may be able to update the row to contain the modified type information (but this should be done under the guidance of Tech Support). - V
... View more
09-20-2011
12:50 PM
|
0
|
0
|
1050
|
|
POST
|
The safest way to add columns to a versioned table is to reconcile and post all your updates, unversion, make the table changes, and re-register the table as versioned. You can't just alter the table, since the ADDs table will not have the parallel columns added. - V
... View more
09-19-2011
11:00 AM
|
0
|
0
|
747
|
|
POST
|
Direct Connect doesn't requrire a hostname, so changing the port often isn't enough. What version of ArcSDE are you using? Is the application server service running? What exact error messages are you receiving (as text, preferrably)? - V
... View more
09-19-2011
10:55 AM
|
0
|
0
|
503
|
|
POST
|
It helps to keep the terminology straight: + ArcSDE operates with 'tables' and 'layers' + ArcGIS operates with 'feature classes' Only ArcGIS can register a new feature class in an ArcSDE geodatabase for editing with ArcGIS (and only with the ArcEditor or ArcInfo license levels). If you are using ArcGIS 10, you don't need to use ArcSDE to access tables with GEOMETRY/ GEOGRAPHY columns -- instead you can use query layers. - V
... View more
09-16-2011
12:33 PM
|
0
|
0
|
2430
|
|
POST
|
There are no ArcSDE command-line utilities which change anything managed by ArcObjects (geodatabases are implemented on top of ArcSDE functionality). - V
... View more
09-16-2011
10:23 AM
|
0
|
0
|
2430
|
|
POST
|
UPDATE and INSERT events don't occur when a versioned table is edited (both are modeled as INSERTs to the Adds tables; UPDATEs also INSERT to the Deletes table). When reconciied, compressed, and posted, the changes are implemented as an INSERT (or DELETE then INSERT in the case of an UPDATE), but this usually occurs *much* later than the original edit. You might experiment with triggers on the Adds table, but that is unsupported (and outside the scope of this thread). - V
... View more
09-14-2011
03:16 AM
|
0
|
0
|
602
|
|
POST
|
There was a recent thread on counting feature classes -- the Python script could be trivially modified to display the objects counted. - V
... View more
09-13-2011
05:33 PM
|
0
|
0
|
741
|
|
POST
|
Desktop licensing determines whether you have privilege to modify tables. I had to enable JavaScript to make Firefox work. - V
... View more
09-08-2011
12:56 PM
|
0
|
0
|
2089
|
|
POST
|
Nothing wrong with those links from here (in IE8 or Firefox 6). Are you using an ArcView license? - V
... View more
09-08-2011
12:37 PM
|
0
|
0
|
2089
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-30-2026 09:35 AM | |
| 2 | 06-08-2026 09:13 PM | |
| 1 | 05-29-2026 12:51 PM | |
| 1 | 06-01-2026 06:03 PM | |
| 2 | 05-29-2026 08:31 AM |