What does and does not get backed up or log shipped in 2005.
1. Will managed code objects get backed up with the database or must the dlls be copied manually? (Answer: They get backed up with the database. No manual backup of the dll files is necessary.)
2. If you have two servers and are using log shipping, how will managed code objects be handled? Will they be available after the log is processed on the other server?
3. Full-text indexing relies on external files which aren't in the logs.
4. What is not handled by log shipping? Anything not handled by log shipping would prevent rapid business or disaster recovery.
5. Will database mirroring replicate absolutely all changes made to the database for a very smooth recovery after failover?
6. How does replication work with the new features? Can replication move new managed code objects to subscribers? How about replication of changes to Service Broker or SSIS?
In general, these questions can be summed up as follows:
1. What does not get backed up as part of a regular database backup?
2. What is not available after failover?
