If you ever need to perform a DR install of SQL to a new path and then restore the system databases, you may encounter these gotchas.
I share these gems that google (and the authors) have wrought:
For SQL 2005 you may learn that the instance cannot find the resource database after you restore the master db. If that is the case, take two aspirin and read this blog post:
Moving the Resource Database in SQL Server 2005
You also may discover that after installing SQL to a new path and restoring the system databases, your jobs won't start. Awesome! Put the whiskey bottle down. Instead, go here and thank Dinesh Asanka and googlefu:
