<?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: Migrating a Versioned SDE database from SDE 9.2 to SDE 9.3.1 in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/migrating-a-versioned-sde-database-from-sde-9-2-to/m-p/106643#M6180</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It is possible to do a direct upgrade from 9.2 to 9.3.1 but since you are also upgrading the database and server it may be easier/cleaner to unversion the data and copy it to the new database.&amp;nbsp; If you work in an environment where there are multiple users you may want them to complete their versions and bring the database to state 0 while you get the new system ready, then copy the data over and grant permissions. That way your downtime is mostly limited to the time it takes you to transfer the data.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Oct 2010 03:42:49 GMT</pubDate>
    <dc:creator>OvidioRivero</dc:creator>
    <dc:date>2010-10-07T03:42:49Z</dc:date>
    <item>
      <title>Migrating a Versioned SDE database from SDE 9.2 to SDE 9.3.1</title>
      <link>https://community.esri.com/t5/data-management-questions/migrating-a-versioned-sde-database-from-sde-9-2-to/m-p/106642#M6179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We are moving from an old SDE 9.2 / SQL 2000 server to servers running SDE 9.3.1 / SQL 2008.&amp;nbsp; Moving non-versioned databases has not been a problem but I haven't tried versioned SDE databases yet.&amp;nbsp; Should I insist that the SDE databases be unverioned before moving to the new servers?&amp;nbsp; On the old servers we used SQL logins but are moving to Windows Authentication on the new.&amp;nbsp; This leaves the versions orphaned in a way when they are restored/upgraded on the new server.&amp;nbsp; Or is this were sp_change_users_login is used?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Sep 2010 16:01:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/migrating-a-versioned-sde-database-from-sde-9-2-to/m-p/106642#M6179</guid>
      <dc:creator>RandyKreuziger</dc:creator>
      <dc:date>2010-09-29T16:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating a Versioned SDE database from SDE 9.2 to SDE 9.3.1</title>
      <link>https://community.esri.com/t5/data-management-questions/migrating-a-versioned-sde-database-from-sde-9-2-to/m-p/106643#M6180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It is possible to do a direct upgrade from 9.2 to 9.3.1 but since you are also upgrading the database and server it may be easier/cleaner to unversion the data and copy it to the new database.&amp;nbsp; If you work in an environment where there are multiple users you may want them to complete their versions and bring the database to state 0 while you get the new system ready, then copy the data over and grant permissions. That way your downtime is mostly limited to the time it takes you to transfer the data.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Oct 2010 03:42:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/migrating-a-versioned-sde-database-from-sde-9-2-to/m-p/106643#M6180</guid>
      <dc:creator>OvidioRivero</dc:creator>
      <dc:date>2010-10-07T03:42:49Z</dc:date>
    </item>
  </channel>
</rss>

