I have a table called Accounts_History that has 10860150 rows right now

and when I run DBCC SHOWCONTIG ('accounts_history'), I got this result

DBCC SHOWCONTIG scanning 'accounts_history' table...
Table: 'accounts_history' (965578478); index ID: 1, database ID: 11
TABLE level scan performed.
- Pages Scanned................................: 894330
- Extents Scanned..............................: 111817
- Extent Switches..............................: 111890
- Avg. Pages per Extent........................: 8.0
- Scan Density [Best Count:Actual Count].......: 99.91% [111792:111891]
- Logical Scan Fragmentation ..................: 0.02%
- Extent Scan Fragmentation ...................: 35.22%
- Avg. Bytes Free per Page.....................: 228.7
- Avg. Page Density (full).....................: 97.17%
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.


Just trying to understand, do I need to rebuild the indexes are it's
perfactly fine or which value indicate I have to rebuild the indexes and all
that.

Please advice

Thanks

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

You are only showing us one output (the clustered index), so this is
the only one we can comment on. Whether or not you have other
(non-clustered) indexes and of so, they are fragmented we can't say.

This index is not fragmented. I prefer to use the Logical Scan
Fragmentation value. See
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.
And if you are on 2005 or later, use sys.dm_db_index_physical_stats
instead.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote