<?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 Alias SQL Instance of Geodatabases in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/alias-sql-instance-of-geodatabases/m-p/824084#M3892</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are moving our SQL Geodatabases from a Physical Machine to a Virtual Machine.&amp;nbsp; &amp;nbsp; The plan is to alias the new VM as the old Physical Server like we have done with many other SQL Servers.&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;It seems this should work as well with Geodatabases.&amp;nbsp; &amp;nbsp;In the example below, the current instance is hpascarcdev.&amp;nbsp; &amp;nbsp; The new VM instance of SQL will have a new name, but with an Alias of hpascarcdev.&amp;nbsp; &amp;nbsp; &amp;nbsp; The existing physical machine will be removed once this upgrade takes place.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any experiences that you can share.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;IMG class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/439168_pastedImage_1.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Mar 2019 23:06:08 GMT</pubDate>
    <dc:creator>MeleKoneya</dc:creator>
    <dc:date>2019-03-11T23:06:08Z</dc:date>
    <item>
      <title>Alias SQL Instance of Geodatabases</title>
      <link>https://community.esri.com/t5/geodatabase-questions/alias-sql-instance-of-geodatabases/m-p/824084#M3892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are moving our SQL Geodatabases from a Physical Machine to a Virtual Machine.&amp;nbsp; &amp;nbsp; The plan is to alias the new VM as the old Physical Server like we have done with many other SQL Servers.&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;It seems this should work as well with Geodatabases.&amp;nbsp; &amp;nbsp;In the example below, the current instance is hpascarcdev.&amp;nbsp; &amp;nbsp; The new VM instance of SQL will have a new name, but with an Alias of hpascarcdev.&amp;nbsp; &amp;nbsp; &amp;nbsp; The existing physical machine will be removed once this upgrade takes place.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any experiences that you can share.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;IMG class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/439168_pastedImage_1.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:06:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/alias-sql-instance-of-geodatabases/m-p/824084#M3892</guid>
      <dc:creator>MeleKoneya</dc:creator>
      <dc:date>2019-03-11T23:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: Alias SQL Instance of Geodatabases</title>
      <link>https://community.esri.com/t5/geodatabase-questions/alias-sql-instance-of-geodatabases/m-p/824085#M3893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I attempted to set this up on my machine and was able to do so along with creating and editing new feature classes. Before committing to this, I would go through a testing procedure to make sure everything seems to be working as this does not look to be a certified approach. If you do happen to run into any issues then please reach out to Esri Tech Support.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2019 21:10:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/alias-sql-instance-of-geodatabases/m-p/824085#M3893</guid>
      <dc:creator>Jared_Motuz</dc:creator>
      <dc:date>2019-03-13T21:10:17Z</dc:date>
    </item>
  </channel>
</rss>

