<?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: GeoDB/DBMS tuning in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32056#M1738</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That article is pretty dated - it appears to have been written for much older versions of ArcGIS and SQL Server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There is really nothing specific to do for SQL Server 2012, other than make sure you apply both ArcGIS 10.1 SP1 and SQL Server 2012 SP1. As it is a new release the first few service packs are useful to apply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The standard geodatabase maintenance tasks apply - maintain statistics, rebuild indexes if the data is changing a lot, and compress regularly.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;And the standard SQL Server tasks apply as well - make sure you have a sound backup and recovery plan, make sure you size your database and logfiles appropriately and do not rely on small autogrowth increments, and keep tempdb on a separate disk if possible.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Shannon&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Nov 2012 22:43:04 GMT</pubDate>
    <dc:creator>ShannonShields</dc:creator>
    <dc:date>2012-11-19T22:43:04Z</dc:date>
    <item>
      <title>GeoDB/DBMS tuning</title>
      <link>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32054#M1736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN style="font-family:Book Antiqua;"&gt;What is the recommended standard tuning needed to be done on a geodatabase on SQL Server 2012 for direct connection or two-tier topology? &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2012 03:46:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32054#M1736</guid>
      <dc:creator>AlaaKutbi</dc:creator>
      <dc:date>2012-11-19T03:46:18Z</dc:date>
    </item>
    <item>
      <title>Re: GeoDB/DBMS tuning</title>
      <link>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32055#M1737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Alaa,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is an older doc, but some of its contents are still applicable:&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://support.esri.com/en/knowledgebase/techarticles/detail/25040"&gt;&lt;BR /&gt;KB #25040 - FAQ: What are some common ArcSDE SQL Server tuning tasks?&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this helps,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2012 15:40:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32055#M1737</guid>
      <dc:creator>DerekLaw</dc:creator>
      <dc:date>2012-11-19T15:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: GeoDB/DBMS tuning</title>
      <link>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32056#M1738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That article is pretty dated - it appears to have been written for much older versions of ArcGIS and SQL Server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There is really nothing specific to do for SQL Server 2012, other than make sure you apply both ArcGIS 10.1 SP1 and SQL Server 2012 SP1. As it is a new release the first few service packs are useful to apply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The standard geodatabase maintenance tasks apply - maintain statistics, rebuild indexes if the data is changing a lot, and compress regularly.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;And the standard SQL Server tasks apply as well - make sure you have a sound backup and recovery plan, make sure you size your database and logfiles appropriately and do not rely on small autogrowth increments, and keep tempdb on a separate disk if possible.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Shannon&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2012 22:43:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geodb-dbms-tuning/m-p/32056#M1738</guid>
      <dc:creator>ShannonShields</dc:creator>
      <dc:date>2012-11-19T22:43:04Z</dc:date>
    </item>
  </channel>
</rss>

