<?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 Best practices for SQL Server on NetApp - Performance? in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10398#M9564</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have SQL 2005 (soon SQL 2008) on a FAS3160 unit, 28 spindles, FC SAN, 15K disks.&amp;nbsp; This is the only host using this storage system.&amp;nbsp; We're probably at 60% of total space capacity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems like since we went live 6 months ago on this storage system (NetApp is new to us), that performance has gradually degraded.&amp;nbsp; SQL Server is increasingly reporting waits from the disk subsystem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any checklist or guide for how to keep your NetApp box running at peak performance, in a SQL Server environment?&amp;nbsp; We do all of the typical SQL Server DBA maintenance (index rebuilds and so on).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:16:15 GMT</pubDate>
    <dc:creator>dnewtontmw</dc:creator>
    <dc:date>2025-06-05T07:16:15Z</dc:date>
    <item>
      <title>Best practices for SQL Server on NetApp - Performance?</title>
      <link>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10398#M9564</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have SQL 2005 (soon SQL 2008) on a FAS3160 unit, 28 spindles, FC SAN, 15K disks.&amp;nbsp; This is the only host using this storage system.&amp;nbsp; We're probably at 60% of total space capacity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems like since we went live 6 months ago on this storage system (NetApp is new to us), that performance has gradually degraded.&amp;nbsp; SQL Server is increasingly reporting waits from the disk subsystem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any checklist or guide for how to keep your NetApp box running at peak performance, in a SQL Server environment?&amp;nbsp; We do all of the typical SQL Server DBA maintenance (index rebuilds and so on).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:16:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10398#M9564</guid>
      <dc:creator>dnewtontmw</dc:creator>
      <dc:date>2025-06-05T07:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for SQL Server on NetApp - Performance?</title>
      <link>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10403#M9565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have Performance advisor in your environment?&amp;nbsp; Are your 28 spindles in a single aggregate or are 14 disks per head?&amp;nbsp; If you've split them in half, then you should have 2x 11 data + 2 Parity + 1 spare?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Apr 2010 04:32:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10403#M9565</guid>
      <dc:creator>evilensky</dc:creator>
      <dc:date>2010-04-04T04:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for SQL Server on NetApp - Performance?</title>
      <link>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10407#M9566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please take a look at this TR: &lt;A href="http://media.netapp.com/documents/tr-3779.pdf" target="_blank"&gt;http://media.netapp.com/documents/tr-3779.pdf&lt;/A&gt;. It also has several links to other useful references. Thanks,&amp;nbsp;&amp;nbsp; -Wei&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Apr 2010 17:10:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10407#M9566</guid>
      <dc:creator>lwei</dc:creator>
      <dc:date>2010-04-04T17:10:33Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for SQL Server on NetApp - Performance?</title>
      <link>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10412#M9567</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'll have to ask the storage team for specifics (I'm more of a SQL guy than storage), but I believe Yes we have performance advisor, and we have a single aggregate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We did read and follow the best practices for SQL on Netapp (the other doc posted), but that's more of a setup and sizing guide.&amp;nbsp; I'm wondering more about ongoing care-and-feeding of NetApp specifically in a SQL environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Apr 2010 20:25:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Best-practices-for-SQL-Server-on-NetApp-Performance/m-p/10412#M9567</guid>
      <dc:creator>dnewtontmw</dc:creator>
      <dc:date>2010-04-04T20:25:53Z</dc:date>
    </item>
  </channel>
</rss>

