<?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: MS SQL Server and Missing SDE 10.1 Base Table in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648552#M36708</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a point feature class in a SQL Express ("Personal ArcSDE") geodatabase.&amp;nbsp;&amp;nbsp; I also get the same error when I attempt to create an ODBC linked table to said feature class from within Access .&amp;nbsp; I'm able to link to all non-spatial tables, even those that are registered with the geodatabase from within the ESRI realm.&amp;nbsp; The two point feature classes in my database have both a clustered index and a spatial index.&amp;nbsp; I suspect that one of those indexes is breaking the ODBC connection.&amp;nbsp; Unlike you, I &lt;SPAN style="text-decoration: underline;"&gt;am&lt;/SPAN&gt; able to see the feature class base tables in SSMS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My work around was to create a view of the feature class in SSMS and then create the ODBC link to the view and not the table.&amp;nbsp; This may not be possibly in your situation since you can't even see the base table in SSMS.&amp;nbsp; However, I first tried creating the view using something to effect of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CREATE VIEW [dbo].[vw_MyView]&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;P&gt;SELECT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.MyFeatureClassBaseTable.*&lt;/P&gt;&lt;P&gt;FROM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.MyFeatureClassBaseTable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was able to create the ODBC link from Access to this view.&amp;nbsp; But when I attempted to edit a cell's value in Access, I was getting some sort of error.&amp;nbsp; I deleted the view and the link&amp;nbsp; and then created a new view that lists all of the columns that I need, such as&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CREATE VIEW [dbo].[vw_MyView]&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;P&gt;SELECT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.Col1, Col2, Col3&lt;/P&gt;&lt;P&gt;FROM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.MyFeatureClassBaseTable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I can edit cell values in Access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ESRI constantly warns users about monkeying with geodatabase tables outside of the ArcGIS environment.&amp;nbsp; I agree that it comes with risks of corruption.&amp;nbsp; But at the same time, SQL is often a much, much more efficient way of managing data.&amp;nbsp; I've been using Access and SSMA to manipulate geodatabase data for over a decade.&amp;nbsp; I have never encountered a problem using Access or SQL as long as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- you don't monkey with any &lt;SPAN style="text-decoration: underline;"&gt;versioned&lt;/SPAN&gt; tables or feature classes in any way&lt;/P&gt;&lt;P&gt;-- you don't delete features in a feature class (sometimes the spatial indexes are in separate tables and the corresponding row would also need to be deleted)&lt;/P&gt;&lt;P&gt;-- you don't add a row to a feature class (for the same reason as above)&lt;/P&gt;&lt;P&gt;-- you don't add a row to a non-spatial table that is registered with the geodb and therefore has an OBJECTID field that ArcGIS libraries should manage&lt;/P&gt;&lt;P&gt;-- you don't delete any tables or FCs that are registered with the geodatabase&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Feb 2015 16:16:42 GMT</pubDate>
    <dc:creator>AZendel</dc:creator>
    <dc:date>2015-02-11T16:16:42Z</dc:date>
    <item>
      <title>MS SQL Server and Missing SDE 10.1 Base Table</title>
      <link>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648551#M36707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is SDE 10.1 for MS SQL Server storing Base Table information differently? I've created a GIS Feature Class that I'm able to view in ArcGIS 10.1. When I go within MS SQL Server Management Studio, the base table is not present. If I go to MS Access to link a table, I can see the feature class table but I receive a "Reserved error -7747; there is no message for this error." when I try to link (ODBC). I'm confused as to why MS Access can see the feature class table and MS SQL Server Management Studio cannot.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for any insight and tips.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2013 18:09:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648551#M36707</guid>
      <dc:creator>JeffCronce</dc:creator>
      <dc:date>2013-02-14T18:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: MS SQL Server and Missing SDE 10.1 Base Table</title>
      <link>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648552#M36708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a point feature class in a SQL Express ("Personal ArcSDE") geodatabase.&amp;nbsp;&amp;nbsp; I also get the same error when I attempt to create an ODBC linked table to said feature class from within Access .&amp;nbsp; I'm able to link to all non-spatial tables, even those that are registered with the geodatabase from within the ESRI realm.&amp;nbsp; The two point feature classes in my database have both a clustered index and a spatial index.&amp;nbsp; I suspect that one of those indexes is breaking the ODBC connection.&amp;nbsp; Unlike you, I &lt;SPAN style="text-decoration: underline;"&gt;am&lt;/SPAN&gt; able to see the feature class base tables in SSMS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My work around was to create a view of the feature class in SSMS and then create the ODBC link to the view and not the table.&amp;nbsp; This may not be possibly in your situation since you can't even see the base table in SSMS.&amp;nbsp; However, I first tried creating the view using something to effect of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CREATE VIEW [dbo].[vw_MyView]&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;P&gt;SELECT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.MyFeatureClassBaseTable.*&lt;/P&gt;&lt;P&gt;FROM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.MyFeatureClassBaseTable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was able to create the ODBC link from Access to this view.&amp;nbsp; But when I attempted to edit a cell's value in Access, I was getting some sort of error.&amp;nbsp; I deleted the view and the link&amp;nbsp; and then created a new view that lists all of the columns that I need, such as&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CREATE VIEW [dbo].[vw_MyView]&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;P&gt;SELECT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.Col1, Col2, Col3&lt;/P&gt;&lt;P&gt;FROM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dbo.MyFeatureClassBaseTable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I can edit cell values in Access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ESRI constantly warns users about monkeying with geodatabase tables outside of the ArcGIS environment.&amp;nbsp; I agree that it comes with risks of corruption.&amp;nbsp; But at the same time, SQL is often a much, much more efficient way of managing data.&amp;nbsp; I've been using Access and SSMA to manipulate geodatabase data for over a decade.&amp;nbsp; I have never encountered a problem using Access or SQL as long as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- you don't monkey with any &lt;SPAN style="text-decoration: underline;"&gt;versioned&lt;/SPAN&gt; tables or feature classes in any way&lt;/P&gt;&lt;P&gt;-- you don't delete features in a feature class (sometimes the spatial indexes are in separate tables and the corresponding row would also need to be deleted)&lt;/P&gt;&lt;P&gt;-- you don't add a row to a feature class (for the same reason as above)&lt;/P&gt;&lt;P&gt;-- you don't add a row to a non-spatial table that is registered with the geodb and therefore has an OBJECTID field that ArcGIS libraries should manage&lt;/P&gt;&lt;P&gt;-- you don't delete any tables or FCs that are registered with the geodatabase&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Feb 2015 16:16:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648552#M36708</guid>
      <dc:creator>AZendel</dc:creator>
      <dc:date>2015-02-11T16:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: MS SQL Server and Missing SDE 10.1 Base Table</title>
      <link>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648553#M36709</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Providing a bit more information would be helpful.&amp;nbsp; You mention ArcSDE 10.1, have you applied any Service Packs or patches?&amp;nbsp; What edition of ArcSDE (Personal, Workgroup, Enterprise)?&amp;nbsp; What version and edition of SQL Server are you using?&amp;nbsp; What version of MS Access are you using?&amp;nbsp; What driver(s) and version(s) have you tried?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Feb 2015 15:21:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648553#M36709</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2015-02-12T15:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: MS SQL Server and Missing SDE 10.1 Base Table</title>
      <link>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648554#M36710</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had experienced the same issue.&amp;nbsp; What I had found was that when I created the view, I had to exclude the Shape field, then I was able to add in and edit the view.&amp;nbsp; Note that this was not a versioned feature layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dale&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2019 14:50:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/ms-sql-server-and-missing-sde-10-1-base-table/m-p/648554#M36710</guid>
      <dc:creator>DaleBridgford</dc:creator>
      <dc:date>2019-02-04T14:50:07Z</dc:date>
    </item>
  </channel>
</rss>

