<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270667#M15627</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No, 'sdetable -o describe' is used to discover columns added with ALTER TABLE&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(after the table has been registered with ArcSDE).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All native geometry column tables which will be registered with ArcSDE &lt;/SPAN&gt;&lt;STRONG&gt;must&lt;/STRONG&gt;&lt;SPAN&gt; have&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;a 32-bit integer NOT NULL rowid column with unique values greater than zero.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Best practice is to &lt;/SPAN&gt;&lt;SPAN style="font-style:italic;"&gt;always&lt;/SPAN&gt;&lt;SPAN&gt; specify the rowid column on the command-line (vice&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;letting 'sdelayer' guess at what column it should use).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the rowid column is of the wrong type a number of strange errors can result&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(including -196 and -114).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Apr 2013 22:08:46 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2013-04-24T22:08:46Z</dc:date>
    <item>
      <title>SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270661#M15621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi, &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;1.&amp;nbsp;&amp;nbsp; I created a table in SQL Server 2008 with a Geography datatype.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Populated it like so (I used the syntax of the SQL Server documentation along with their defined polygon):&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN style="font-style:italic;"&gt;INSERT INTO EntireTripExtent (geom)&lt;BR /&gt;VALUES (geography::STGeomFromText('POLYGON((-122.358 47.653, -122.348 47.649, -122.348 47.658, -122.358 47.658, -122.358 47.653))', 4326));&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;2.&amp;nbsp; And then from Catalog exported it from the db into an sde db.&lt;BR /&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;3.&amp;nbsp; Then I tried to run the following registerlayer command (with a correct user and password):&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN style="font-style:italic;"&gt;sdelayer -o register -l EntireTripExtent,geom -e a -i sde:sqlser&lt;BR /&gt;ver:gis-data -s gis-data -D transportationSystems -u user -p pass&lt;BR /&gt; -t GEOGRAPHY&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;STRONG&gt;I get the following error:&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN style="font-style:italic;"&gt;ArcSDE 10.0&amp;nbsp; for SQL Server Build 685 Fri May 14 12:05:43&amp;nbsp; 2010&lt;BR /&gt;Layer&amp;nbsp;&amp;nbsp;&amp;nbsp; Administration Utility&lt;BR /&gt;-----------------------------------------------------&lt;BR /&gt;Error: Invalid layer storage type (-196).&lt;BR /&gt;Error: Cannot Create Layer.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I cannot find any information as to what might be causing this error.&amp;nbsp; The documentation is not very good!&amp;nbsp; I could only guess at what the right extent was for a polygon (I chose area). I could not find any description as to what extent was used for.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anyone have any ideas what I might be doing wrong?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sera&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 19:55:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270661#M15621</guid>
      <dc:creator>SeraWhite</dc:creator>
      <dc:date>2011-03-02T19:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270662#M15622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Interesting.&amp;nbsp; If I add dbo. to the tablename I get a new error:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-style:italic;"&gt;Error Wrong Column Type (-114)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 21:10:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270662#M15622</guid>
      <dc:creator>SeraWhite</dc:creator>
      <dc:date>2011-03-02T21:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270663#M15623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Sera, &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm getting the exact same error message, trying to do the same thing, and yours is the only reference I can find on the whole interweb.&amp;nbsp; Do you remember how you solved this issue (if you did at all)? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-update: okay, my problem was related to not have a integer row id in my table. I edited the SDE_table_registry to add a rowid_column value for my table.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 12:43:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270663#M15623</guid>
      <dc:creator>MichaelBlom</dc:creator>
      <dc:date>2011-09-21T12:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270664#M15624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Editing the SDE_* and GDB_* tables is very much not recommended (and almost never necessary).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The supported mechanism for acknowledging new columns is to run 'sdetable -o describe' as the &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;table owner.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 21:02:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270664#M15624</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2011-09-21T21:02:27Z</dc:date>
    </item>
    <item>
      <title>Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270665#M15625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I never did solve the problem.&amp;nbsp; I approached it from a completely different angle.&amp;nbsp; Your solution is interesting.&amp;nbsp;&amp;nbsp; I don't think I would have thought about that.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for posting the update. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sera&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 22:41:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270665#M15625</guid>
      <dc:creator>SeraWhite</dc:creator>
      <dc:date>2011-09-21T22:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270666#M15626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Editing the SDE_* and GDB_* tables is very much not recommended (and almost never necessary).&lt;BR /&gt;The supported mechanism for acknowledging new columns is to run 'sdetable -o describe' as the &lt;BR /&gt;table owner.&lt;BR /&gt; &lt;BR /&gt;- V&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You run 'sdetable -o describe' to address the Invalid layer storage type??&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Apr 2013 21:52:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270666#M15626</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2013-04-24T21:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: SDE 10, SQL Server Geography datatype Invalid Layer Storage Type</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270667#M15627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No, 'sdetable -o describe' is used to discover columns added with ALTER TABLE&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(after the table has been registered with ArcSDE).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All native geometry column tables which will be registered with ArcSDE &lt;/SPAN&gt;&lt;STRONG&gt;must&lt;/STRONG&gt;&lt;SPAN&gt; have&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;a 32-bit integer NOT NULL rowid column with unique values greater than zero.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Best practice is to &lt;/SPAN&gt;&lt;SPAN style="font-style:italic;"&gt;always&lt;/SPAN&gt;&lt;SPAN&gt; specify the rowid column on the command-line (vice&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;letting 'sdelayer' guess at what column it should use).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the rowid column is of the wrong type a number of strange errors can result&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(including -196 and -114).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Apr 2013 22:08:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-10-sql-server-geography-datatype-invalid-layer/m-p/270667#M15627</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2013-04-24T22:08:46Z</dc:date>
    </item>
  </channel>
</rss>

