Area Maintenance Plans Stored procedure based solution
Logging The log file is created in the end of the Maintenance Plan execution. If the Maintenance Plan, SQL Server or server would crash then you have no log file.

The logging includes superficial information about the execution. 		The log file is created in the beginning of the stored procedure execution. Log information is written as the stored procedure execution proceeds.

The logging includes start time, command text, command output and end time for each command.
Database Selection You can select databases as below.

All databases
All system databases
All user databases
A list of databases 		You can select databases as below.

All databases
All system databases
All user databases
A list of databases
Exclusion of databases
Database name wildcard selection
Error Handling If an error occur the Maintenance Plan continues to the next database and reports failure in the end.

If the backup fails for one database, the other databases will still be backed up. 		If an error occur the stored procedure logs the error, continues to the next database and reports failure in the end.

If the backup fails for one database, the other databases will still be backed up.
Backup Compression The Maintenance Plan supports native SQL Server 2008 backup compression. The backup stored procedure supports native SQL Server 2008 backup compression and LiteSpeed backup compression.
Online Index Rebuild In the Maintenance Plan you can select to do rebuild of indexes online or offline.

The problem with that is that if the index (or table for a clustered index) contains a LOB (large object), online rebuild is not supported and will fail.		 The index optimization stored procedure supports dynamic online / offline rebuild of indexes based on LOB (large object) existence.

It supports that indexes with no LOBs are rebuilt online and indexes with LOBs are rebuilt offline.
Index Fragmentation The Maintenance Plan does not take index fragmentation into consideration when rebuilding and reorganizing indexes. The index optimization stored procedure supports dynamic rebuild / reorganization of indexes based on the fragmentation levels.

It supports that indexes with a high level of fragmentation are rebuilt, that indexes with a medium level of fragmentation are reorganized and that indexes with a low level of fragmentation are skipped.
Partitioning The Maintenance Plan rebuilds and reorganizes partitioned indexes on the table level (not partition level). The index optimization stored procedure supports both table level and partition level rebuild and reorganizition of partitioned indexes.
Documentation SQL Server Books Online Documentation