How does this solution for backup, integrity check and index optimization do against the SQL Server 2005 Maintenance Plans? I have compared the two solutions.

Area	Maintenance Plans	Stored procedure based solution
Logging	The log file is created in the end of the Maintenance Plan execution. The logging includes superficial information about the execution. This means that if the Maintenance Plan, SQL Server or server would crash then you have no log file.	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. All information is written to the log file instantly.
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 All system databases, except a list of databases All user databases, except a list of databases This means that if you have one database that should have one backup strategy and some other databases that should have another backup strategy, this can be easily configured.
Error Handling	If an error occur the Maintenance Plan continues to the next database and reports failure in the end. This means that if you have a corruption issue with one database, the other databases will still be checked.	If an error occur the stored procedure logs the error, continues to the next database and reports failure in the end. This means that if you have a corruption issue with one database, the other databases will still be checked.
Online Index Rebuild	In the Maintenance Plan you can select to do rebuild of indexes online or offline. The problem with that is that as if the index (or table for clustered indexes) 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. This means that it supports that indexes with no LOBs can be rebuilt online and indexes with LOBs can be rebuilt offline.
Index Fragmentation	The Maintenance Plan does rebuild and reorganize of indexes regardless of fragmentation levels.	The index optimization stored procedure supports dynamic rebuild or reorganize of indexes based on fragmentation level. This means that it can be configured to rebuild indexes with a high level of fragmentation, reorganize indexes with a medium level of fragmentation and do nothing about indexes with a low level of fragmentation.
Documentation	SQL Server Books Online	Documentation