https://www.sqlserver70.com/tags/compatibility-views/Recent content in Compatibility Views on SQL Server ScriptsHugo -- gohugo.ioenSQLServer70.comMon, 15 Jun 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-sysindexes-vs-sys-indexes-catalog-views/Mon, 15 Jun 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-sysindexes-vs-sys-indexes-catalog-views/ <p>Plenty of SQL Server scripts still in circulation read <code>rowcnt</code> and <code>dpages</code> straight out of <code>sysindexes</code> — a habit inherited from SQL Server 2000, where that table was the canonical place to find row counts and page totals. The object survives only as the <code>sys.sysindexes</code> compatibility view, is flagged for removal, and returns inaccurate numbers for partitioned tables. This post shows the modern replacement and how to migrate.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:inline-block;width:728px;height:90px" data-ad-client="ca-pub-1012089347386563" data-ad-slot="8593449130"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>In SQL Server 2000, <code>sysindexes</code> was a real system table with one row per index and heap, and DBAs leaned on its <code>rowcnt</code>, <code>dpages</code>, <code>reserved</code>, and <code>used</code> columns for quick size and row-count reports. SQL Server 2005 rebuilt the metadata layer, and <code>sysindexes</code> was retained only as <code>sys.sysindexes</code>, a backward-compatibility view. Microsoft's documentation is explicit: this feature is included for backward compatibility, will be removed in a future version, and should not be used in new development.</p>