<?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 replication lag issue due to sql server defrag job in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/replication-lag-issue-due-to-sql-server-defrag-job/m-p/45172#M4872</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had twice a week large replication lag of a few hours and snapshots not completing due to twice a week sql server database defrag jobs. It is obvious that Defrag changes a lot of data.&amp;nbsp;&amp;nbsp; Our sql dba uses defrag job for our production databases for many years. There is no replicon issue for using our previous storage system -- HP&amp;nbsp; EVA CA (continue access)&amp;nbsp; technology until we migrated out storage system&amp;nbsp; to Netapp last Christmas.&amp;nbsp; What is the best practice for this?&amp;nbsp; Should we continue to run defrag for our sql server production database? Can we skip sql server database defrag job?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Any advice and help would be appreciated.&amp;nbsp; We would like to hear other experienced sql server DBA share their bast practice on defrag job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; We were told by vendor that we should try to run database&lt;BR /&gt;defrag job less frequent using Netapp storage system compared with our previous&lt;BR /&gt;HP EVA storage system. Is there any system performance impact without running&lt;BR /&gt;database defrag? The total size for all databases is not big with only 50 GB.&lt;BR /&gt;Please share your knowledge and best practice.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:33:03 GMT</pubDate>
    <dc:creator>HGUO_LSAC</dc:creator>
    <dc:date>2025-06-05T05:33:03Z</dc:date>
    <item>
      <title>replication lag issue due to sql server defrag job</title>
      <link>https://community.netapp.com/t5/Data-Protection/replication-lag-issue-due-to-sql-server-defrag-job/m-p/45172#M4872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had twice a week large replication lag of a few hours and snapshots not completing due to twice a week sql server database defrag jobs. It is obvious that Defrag changes a lot of data.&amp;nbsp;&amp;nbsp; Our sql dba uses defrag job for our production databases for many years. There is no replicon issue for using our previous storage system -- HP&amp;nbsp; EVA CA (continue access)&amp;nbsp; technology until we migrated out storage system&amp;nbsp; to Netapp last Christmas.&amp;nbsp; What is the best practice for this?&amp;nbsp; Should we continue to run defrag for our sql server production database? Can we skip sql server database defrag job?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Any advice and help would be appreciated.&amp;nbsp; We would like to hear other experienced sql server DBA share their bast practice on defrag job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; We were told by vendor that we should try to run database&lt;BR /&gt;defrag job less frequent using Netapp storage system compared with our previous&lt;BR /&gt;HP EVA storage system. Is there any system performance impact without running&lt;BR /&gt;database defrag? The total size for all databases is not big with only 50 GB.&lt;BR /&gt;Please share your knowledge and best practice.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:33:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/replication-lag-issue-due-to-sql-server-defrag-job/m-p/45172#M4872</guid>
      <dc:creator>HGUO_LSAC</dc:creator>
      <dc:date>2025-06-05T05:33:03Z</dc:date>
    </item>
  </channel>
</rss>

