New answers tagged fragmentation
As Kin noted above, it is not possible to get this information since it is not stored by SQL Server. Please refer to this article on technet. Since you are using Ola's scripts, unless you changed the defaults, the output of the IndexOptimize job should go to the same location as your error log.
SQL Server does not maintain when an Index was last rebuild, instead it keeps information when stats were last updated. That can be found using the STATS_DATE function. You can use Ola's Index maintenance solution or Michelle Ufford's - Index Defrag Script. These scripts are widely tested in the community and are much flexible so that you can adapt as per ...
The lazy answer: You can use the Segment Advisor recomendations. Can be viewed in OEM, DBA_ADVISOR_RECOMMENDATIONS, o DBMS_SPACE.ASA_RECOMMENDATIONS procedure. https://docs.oracle.com/cd/E18283_01/server.112/e17120/schema003.htm You can also build your own script gathering data, joining, and do calcs from several storage related dictionary views, but, ...
Yes, you can stop a reorganize and it won't cause a big rollback like you are talking about. You will be left with where the operation left off (that's a good thing). It's a rebuild that would have the rollback behavior.
Top 50 recent answers are included