jasona.work (5/1/2016)
First up, Phil has it right. Get backups of *ALL* the databases on the server and test restore them. It doesn't have to be to a "server," they could have someone set up SQL2005 on their desktop machine and restore there. Make sure the backups are good!Boiling it down, in order of importance, I'd:
1. Set up backups of all the databases
2. Test those backups on another system (server, desktop, someone's spare laptop from home, doesn't matter)
3. Investigate the cause of the BSODs (could be a fixable hardware issue)
The other thing is, as they're on SQL2005, they're either going to have to scrounge up a SQL2005 Developer Edition, violate licensing and install their existing copy on that 2nd PC, or if someone has an MSDN Subscription they might be able to get a copy from there.
But the point they need to keep in mind is not "fix the server," it's PROTECT THE DATA. And that means making sure not only that it's being backed up, but that it can be restored and used.
Thanks for your response.
I think that "PROTECT THE DATA" is the least of their problems.......this can easily be reloaded via the ETL scripts in SSIS. This is only a reporting system and is non transactional
Unless a full backup of SQL dbs and system dbs already covers the below requirements what do they need to do for the following......
recreate linked servers
recreate all users and logins
recreate all SSIS packages
recreate all SSAS cubes
recreate all SQL agent jobs
thanks
________________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day