<?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: SQL Server st_transform equilavent in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/sql-server-st-transform-equilavent/m-p/828835#M4147</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jeff,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, Microsoft does not allow transformations through their ST functions like we do for Oracle and PostgreSQL DBMS's.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only workaround that is going to work here is to use 2 spatial columns in the table in SQL Server. While we do not support multiple spatial columns when working with tables or views in ArcGIS, Microsoft does. So you could add a second spatial column in the WKID that you need and then create a view or query layer using only one of those columns for use in ArcGIS. Outside of this though, I can't think of another way around it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jonathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Sep 2018 16:15:37 GMT</pubDate>
    <dc:creator>JonathanFarmer_oldaccount</dc:creator>
    <dc:date>2018-09-06T16:15:37Z</dc:date>
    <item>
      <title>SQL Server st_transform equilavent</title>
      <link>https://community.esri.com/t5/geodatabase-questions/sql-server-st-transform-equilavent/m-p/828834#M4146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have been encourage to migrate from Oracle to SQL server for multiple reasons.&amp;nbsp; In doing a gap analysis, most of what we do seems pretty transportable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The one thing we seem to be missing is sde.st_transform.&amp;nbsp; We keep our data natively in State Plane, but create spatial views to show the data in different coordinate systems, or to add Lat/Long coordinates, or to union datasets in different systems.&amp;nbsp; This is an absolute necessity to be able to do live.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any solution at all ?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Sep 2018 20:32:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/sql-server-st-transform-equilavent/m-p/828834#M4146</guid>
      <dc:creator>JeffPace</dc:creator>
      <dc:date>2018-09-05T20:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server st_transform equilavent</title>
      <link>https://community.esri.com/t5/geodatabase-questions/sql-server-st-transform-equilavent/m-p/828835#M4147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jeff,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, Microsoft does not allow transformations through their ST functions like we do for Oracle and PostgreSQL DBMS's.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only workaround that is going to work here is to use 2 spatial columns in the table in SQL Server. While we do not support multiple spatial columns when working with tables or views in ArcGIS, Microsoft does. So you could add a second spatial column in the WKID that you need and then create a view or query layer using only one of those columns for use in ArcGIS. Outside of this though, I can't think of another way around it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jonathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2018 16:15:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/sql-server-st-transform-equilavent/m-p/828835#M4147</guid>
      <dc:creator>JonathanFarmer_oldaccount</dc:creator>
      <dc:date>2018-09-06T16:15:37Z</dc:date>
    </item>
  </channel>
</rss>

