I think you've hit the nail on the head there Michelle, at present I am trying to persuade the "decision makers" in our buisness to make available more resources & or budget to review and complete our DR plans. 

As a mainly Oracle based company the smaller SQL Server environment is seen to not be business critical, even though a number of the SQL systems are both business critical and feeder systems to the Oracle production servers.  When I approached the Oracle team about "there" DR plans, they replied with "we have all that, we created it all when we implemented", this was about 4 years ago (currently they are also half way through a massive upgrade project, which has no DA plans).  I have subsequently taken it on myself to begin developing a DA plan which I hope will become a continuous project with a rolling scope, i.e Phase 1 will be to develop the necessary DR plan(s) and required processes from a SQL Server standpoint, Phase 2 will incorporate .NET applications using the SQL Server db's, Phase 3 will include associated systems, i.e. Oracle, Reporting, etc.. Phase 4 will include the IT Infrastructure supporting all previous systems, then finally Phase 5 will incorporate any business processes/systems left out of the previous phases, by then it will most probably be necessary to begin at Phase 1 again and work through the DR plan(s) reviewing there correctness, scope and validity.  I feel this will be the best approach to getting the "buy in" from the business.  Any ideas/comments/thoughts on this proposed method of attack would be greatfully appreciated.

Cheers,

Lloyd

p.s. Is anyone aware of some good resources, i.e. articles, books, papers related to disaster recovery?  I have done some limited research on the internet and have found some useful articles/documents but would appreciate any more resources.