Use this script and the results will match ..

SELECT

db_name() AS DbName,

SCHEMA_NAME(B.schema_id) AS SchemaName

, B.name AS TableName

, C.name AS IndexName

, A.INDEX_DEPTH as Index_depth

, C.fill_factor AS IndexFillFactor

, D.rows AS RowsCount

, A.avg_fragmentation_in_percent

, A.page_count

, GetDate() as [TimeStamp]

FROM sys.dm_db_index_physical_stats(DB_ID(),NULL,NULL,NULL,NULL) A

INNER JOIN sys.objects B

ON A.object_id = B.object_id

INNER JOIN sys.indexes C

ON B.object_id = C.object_id AND A.index_id = C.index_id

INNER JOIN sys.partitions D

ON B.object_id = D.object_id AND A.index_id = D.index_id

WHERE C.index_id > 0 and A.INDEX_DEPTH >2

ORDER BY A.avg_fragmentation_in_percent DESC

Tables will be automatically available for use once the rebuild completes. No extra steps needed.

Instead of using Maintenance Plans try to use Index Maintenance solution from Ola Hallengren which is customizable and gives you more control and better logging.

http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html

It depends on your environment. Even though Rebuild Index will update statistics it doesn't update NonIndex-column statistics. May be if you can update statistics on a nightly basis you need not do it immediately after the index rebuilds.

--

SQLBuddy