Script to retrieve the Maintenance Jobs

select

LastRunTime,

CASE OperationType
       WHEN 14 THEN 'DeletionService'
       WHEN 15 THEN 'IndexManagement'
       WHEN 30 THEN 'ReindexAll'
       WHEN 32 THEN 'CleanupInactiveWorkflowAssemblies'
       WHEN 40 THEN 'GoalRollup'
END OperationType, OperationType

,

enabled, ExecutionTime,LastResultCode,LastResultData
,MaintenanceWindowEndTime,MaintenanceWindowStartTime, ModifiedOn
,NextRunTime,RecurrencePattern, RecurrenceStartTime, StartedOn, State, IsDeleted

 from ScaleGroupOrganizationMaintenanceJobs


 order by LastRunTime desc

The jobs below are run by CRM async Service (Maintenance)

Maintenance Job Name	Purpose	Default Frequency/ Recommendation	Operation Type
Deletion Service	The deletion service maintenance operation now cleans up subscription tracking records for deleted metadata objects as they expire. ·         If Outlook does not sync for 90 days, the job will remove the subscription with CRM. ·         Cleanup POA records. Un-sharing of record(s) do not remove the records in the POA table, it will stay there for 90 days and it will clean up by the deletion job. ·         Cleanup failed/stuck workflows for the record(s) synchronize with Outlook.	By default, the job executes every 24 hours, reschedule the job to run at non-peak hours. E.g. 11:00PM at night	14
Indexing Management	Validates that system-managed indexes exist for all entities and recreates any missing indexes. This is more for CRM Online and only impacts us during configuration of the solution. It automatically creates index for each column used in search for Quick Find if the index is not already created in the CRM database	By default, the job executes every 24 hours, reschedule the job to run at non-peak hours. E.g. 11:00PM at night	15
Organization Full Text Catalog Index	Full Text Catalog Index		25
Reindex All	Reorganizes/rebuilds fragmented indexes depending on the amount of fragmentation. It execute the p_ReindexAll stored procedure, it selects all indexes in the database with greater than 30% fragmentation and runs ReIndex on each while in online mode. Run while online mode means indexes are not taken offline while reindex is happening they still are active and are functioning and can be used. Large enterprise CRM implementation with big data volume should disable this CRM reindex job if a custom job is created for recreating the indexes and with run update stats.	By default, the job executes every 24 hours, disable the job by setting the Job Next Run value to the future. E.g. 12/31/2999	30
Cleanup Inactive Workflow Assemblies	Seeks custom workflow assemblies that are no longer referenced in workflow rules or in-process jobs. Those unreferenced assemblies are then deleted. Consider the scenario where you register version 2.0 of a custom workflow assembly.  You may update your rules to reference the new version, but some in-progress jobs may still be referencing version 1.0.  Once those jobs have completed, this maintenance job will clean up the version 1.0 assembly that is no longer referenced by rules/jobs. It executes the p_CleanupInactiveWorkflowAssembliesstored procedure.	By default, the job executes every 24 hours, reschedule the job to run at non-peak hours. E.g. 11:00PM at night	32
Create Audit Partition	Alters the partitioning scheme for the auditbase table (SQL Enterprise only).	By default, the job executes every month, reschedule the job to run at non-peak hours. E.g. 11:00PM at night
Check for MUI Updates	Detects upgrades to language (MUI) packs and schedules additional async operations to perform individual language provisioning.	By default, the job executes every 24 hours, if you don’t have language pack installed, you can disable the job by setting the Job Next Run value to the future. E.g. 12/31/2999
Refresh Entity Row Count	Refreshes the Record Count snapshot statistics leveraged enhanced query plans. This job is important because it define how Quick Find works, it uses the counts to come up with the correct query plan.	By default, the job executes every 24 hours, reschedule the job to run at non-peak hours. E.g. 11:00PM at night
Refresh Sharing Count	Refreshes the POA read snapshot statistics leveraged in enhanced query plans. This job is important because it define how Quick Find works, it uses the counts to come up with the correct query plan.	By default, the job executes every 24 hours, reschedule the job to run at non-peak hours. E.g. 11:00PM at night