Am sure every DBA has once in his/her career come across a situation of recovering a database or an instance of a database server. Reasons may vary for the database or server to go offline. However at times like a Windows Host Crash where the DBA's are required to rebuild an entire database instance from scratch below details may come in handy for rebuilt purposes.
1. SQL version, port, memory and cpu details (available in the verification documents & cmdb entries)
2. Drive & space information
3. Number of instances installed
4. Instance specific non-default configuration details(Eg:32-bit,64-bit Aliases)
5. SQL service information (If the host also deployed SSIS & SSRS)
6. Latest verified backups for system and user databases.
7. Any external drive mapping details
8. SSIS or DTS local package information and files
9. SSRS local reports and projects
10 SSIS/SSAS local projects
10. Local application queries if any
11. SQL aliases configuration details
(Note: Any SQL DR strategy deployed should also provide the above information if configured wisely )
It's wise to have the inventory updated and maintained with all these details to avoid running around for the same.There could be many more details however these are the top few that occur to me when I hear System Crash 🙂
