I am considering log shipping MSDB and wonder if anybody has tried it and could comment on it. I know a lot of poeple assume it is not feasible but it might be a limitation of the GUI of SSMS. In 2008, it is possible to script log shipping and configure it to restore to a database named differently than the original one. This would allow not to overwrite MSDB on the destination server by naming the destination database differently, for instance MSDB_DifferentlyNamed, and therefore not break the log shipping requirements. Log shipping needs access to MSDB on both primary and secondary server. SQL server 2008 does not seem to allow log shipping for msdb via the SSMS GUI. I believe it is due to the fact that the GUI does not allow to select a different name than the original database for the destination database. This would mean that MSDB would need to be sent in restoring state on the destination server, hence preventing it's usage which is required for log shipping in the first place. Now, what I am wondering is if one can do it, if he should do it. In other word, anybody tried or has reliable info on why one should or should not do it? Is the GUI not allowing log shipping of SSMS because of previous consideration which have not been revised or is there more to it which would make it not recommanded. Thanks.