Schedule Maintenance Plan - Request For a Good Sequence I have installed Ola Hallengren's MaintenanceSolution.sql script. 

So what I'll get out-of-the-box are a lot of jobs:  

 

My questions is: 

What schedules should I implement based on the jobs that are provided with the script?  

The SQL-Full Backup starts on Saturday at 11:00 pm. So I thought I would use the following schedules:

Job                           Schedule
----------------------------- ------------------------
IndexOptimize                 Saturday at 10:00 pm  
Database IntegrityCheck       Saturday at 09:00 pm  
CommandLog Cleanup            Sunday at 03:00 am  
Output File Cleanup           Sunday at 03:15 am  
SP_delte_backuphistory        Sunday at 03:20 am  
SP_purge_Jobhistory           Sunday at 03:25 am  


What's your advice? 

Every comment is welcome.
It looks like your goal is to "chain" certain jobs: to run an integrity check, then an index optimization, then a backup.

First - it may make sense to take a backup before the check and index optimization. If something were to go horribly wrong during those steps, you could get back to the start to try to resolve things. If you take differential backups of this DB, you might want to take a final diff backup before, and a full backup after.

Second, the chaining seems reasonable in general. However, until you've run the jobs, you have no idea how long they'll take. If there's a chance that the DB check and the index optimization could take longer than an hour, I'd space things out more. Overlapping these things isn't necessarily a good idea.

If the tightest possible chaining is desirable, then move the job steps into a single job, and order them as desired. Or, as suggested by @AaronBertrand, only set and actual schedule for the first job; have the first job kick off the second as its final step, the second job kick off the third, and so forth.