<?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: Views, SQL Server Express, and SDE 10.1 in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370953#M21080</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;What kind of view?&amp;nbsp; It sounds like you want a UNION ALL join, which is tricky, at best.&lt;BR /&gt;&lt;BR /&gt;Best practice for views is often to use native geometry, edit the view natively, then&lt;BR /&gt;register it when you've got it working correctly.&amp;nbsp; For SDEBINARY storage, this wouldn't&lt;BR /&gt;work, and you're tightly constrained on how you can create the view (I'll generally &lt;BR /&gt;make a fake table with the columns defined as I'll need them, join that in a view,&lt;BR /&gt;then edit the view after, but you have to be *really* careful not to break the view).&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;I should explain more clearly, here is what I would like to do:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have 5 Feature Classes (all Lines) in the Geodatabase:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Water Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Gas Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Sanitary Sewer Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Air Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Chemical Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would like my users to be able to access these layers as a read only (Select only), no editing, for use in InforEAM 8.5 Asset Management GIS Module which accesses ArcGIS Server 10.1 via a Map Service (which ties directly to the MXD, as you know). But, the trick is I want the user to see these Feature Classes inside the InforEAM Map Window as "one Feature Class", remember these are separate Feature Classes in the Geodatabase. I assume creating a View from these 5 Feature Classes is the correct approach?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Sep 2012 22:04:36 GMT</pubDate>
    <dc:creator>TimHayes</dc:creator>
    <dc:date>2012-09-14T22:04:36Z</dc:date>
    <item>
      <title>Views, SQL Server Express, and SDE 10.1</title>
      <link>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370951#M21078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Can SDE 10.1 used with SQL Server Express generate Views? I have multiple feature classes in an SDE/SQL Server Express Geodatabase and would like certain records to be "collated" into a View for the user to access inside one of my ArcGIS Server Flex Map Viewers.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Sep 2012 19:38:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370951#M21078</guid>
      <dc:creator>TimHayes</dc:creator>
      <dc:date>2012-09-14T19:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: Views, SQL Server Express, and SDE 10.1</title>
      <link>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370952#M21079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;What kind of view?&amp;nbsp; It sounds like you want a UNION ALL join, which is tricky, at best.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best practice for views is often to use native geometry, edit the view natively, then&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;register it when you've got it working correctly.&amp;nbsp; For SDEBINARY storage, this wouldn't&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;work, and you're tightly constrained on how you can create the view (I'll generally &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;make a fake table with the columns defined as I'll need them, join that in a view,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;then edit the view after, but you have to be *really* careful not to break the view).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Sep 2012 20:47:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370952#M21079</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2012-09-14T20:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: Views, SQL Server Express, and SDE 10.1</title>
      <link>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370953#M21080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;What kind of view?&amp;nbsp; It sounds like you want a UNION ALL join, which is tricky, at best.&lt;BR /&gt;&lt;BR /&gt;Best practice for views is often to use native geometry, edit the view natively, then&lt;BR /&gt;register it when you've got it working correctly.&amp;nbsp; For SDEBINARY storage, this wouldn't&lt;BR /&gt;work, and you're tightly constrained on how you can create the view (I'll generally &lt;BR /&gt;make a fake table with the columns defined as I'll need them, join that in a view,&lt;BR /&gt;then edit the view after, but you have to be *really* careful not to break the view).&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;I should explain more clearly, here is what I would like to do:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have 5 Feature Classes (all Lines) in the Geodatabase:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Water Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Gas Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Sanitary Sewer Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Air Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Chemical Pipes&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would like my users to be able to access these layers as a read only (Select only), no editing, for use in InforEAM 8.5 Asset Management GIS Module which accesses ArcGIS Server 10.1 via a Map Service (which ties directly to the MXD, as you know). But, the trick is I want the user to see these Feature Classes inside the InforEAM Map Window as "one Feature Class", remember these are separate Feature Classes in the Geodatabase. I assume creating a View from these 5 Feature Classes is the correct approach?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Sep 2012 22:04:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370953#M21080</guid>
      <dc:creator>TimHayes</dc:creator>
      <dc:date>2012-09-14T22:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: Views, SQL Server Express, and SDE 10.1</title>
      <link>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370954#M21081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;So all these tables have identical attributes, and have been implemented using GEOMETRY &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;storage with identical parameters?&amp;nbsp; And none of them are versioned?&amp;nbsp; And they've all been&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;configured with different, non-overlapping rowid sequences?&amp;nbsp; Then if Microsoft supports &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;UNION ALL views with GEOMETRY, and the performance is adequate, it might be possible&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to register the resulting view.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But you'd still get better performance if you appended the various pieces into a new single&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;table, and set up a replication mechanism for this "materialied view" from the component &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;tables.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Sep 2012 00:37:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370954#M21081</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2012-09-15T00:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: Views, SQL Server Express, and SDE 10.1</title>
      <link>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370955#M21082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;So all these tables have identical attributes, and have been implemented using GEOMETRY &lt;BR /&gt;storage with identical parameters?&amp;nbsp; And none of them are versioned?&amp;nbsp; And they've all been&lt;BR /&gt;configured with different, non-overlapping rowid sequences?&amp;nbsp; Then if Microsoft supports &lt;BR /&gt;UNION ALL views with GEOMETRY, and the performance is adequate, it might be possible&lt;BR /&gt;to register the resulting view.&lt;BR /&gt;&lt;BR /&gt;But you'd still get better performance if you appended the various pieces into a new single&lt;BR /&gt;table, and set up a replication mechanism for this "materialied view" from the component &lt;BR /&gt;tables.&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;The answer! thanks! your idea about the single table is brilliant. I will look into this in more detail. I think it just might work.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Sep 2012 01:26:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/views-sql-server-express-and-sde-10-1/m-p/370955#M21082</guid>
      <dc:creator>TimHayes</dc:creator>
      <dc:date>2012-09-15T01:26:43Z</dc:date>
    </item>
  </channel>
</rss>

