SQL Server Crashes and Critical Failures (Udemy.com)

The quality of these courses is high. I especially like the way they organized the quizzes; the results in the quizzes summarize the answers, so you can not only see your rating but also read about your strenghts and weaknesses.

I enjoy the real world aspect of his style, but this tutorial could have used more explanations about 'why.' For example, when talking about "Restoring the Resource DB" there was no explanation as to how/why you might end up needed to do that. But still worth while.

As per my opinion this is must course for those who are just started learning about the DBA Role for those who want to enhance their skills in this Role. I would like to thank mike for designing such a wounderful and such a informative course for us.

Excellent. I thought the course was concise and to the point, with clear diction and good pacing. I really liked that important or complex commands were displayed in notepad and pasted in as needed. Not only did this prevent typos but it let everyone see things in advance. IMHO, there is no value in seeing an instructor type in every single command. My only complaint is that there were quite a number of typos in the quizzes. This did not detract from the value of the course, but as everything else was so good - why not go that extra 10%?

Experienced teacher, I liked the class format and the basic introduction to the command line to restore the master db as well as to create the SA Password. Perhaps another class can be teached focusing deeper on the command line to solve other db problems.

The instructor explain very well things that can happen and allow the students to practice some procedures. The course was introductional, but teach the first steps to familiarize with SqlServer internals diagnostics tools, and explain the system databases very well. The exercises proposed are very suncint but are good because these procedures are not used in normal sql operation, and having a good reference can help us in critical cases. The reference about permisions is a very common case, and was a good topic explained. In overall is a good course both for beginers as for advanceds, as an refresher of some things. This course dont explain how to recover a user database, and is focused in how to start up the instance if some system database or resource fails. User database recovery procedures was out of the scope of the course. But the course is good since without instance running, we can't proceed in any another diagnostics.

The course does provide some good basic knowledge and ways to recover from crash. However, the total course length of 1hour limits Mike from discussing more scenarios. The lessens' duration has been kept small so that you can watch them all in less number sittings without getting bored. Would live see some. Thanks Mike.

the course provided what it said it would in the outline. excellent information and easy to follow especially for a free course. May need another course link on how to prevent SQL crash by "how to backup your user and system databases" a best practice if you will...

Clear, concise and informative. The course covers some very important topics and not only made me understand them better but actually made them easy. I have no doubts or worries now when presented with the dreaded scenario of recovering the Master database.

Course is good for Junior Level DBA as it covers some very important points. Of all the points, recovering and rebuilding master is the most important. My technique is slightly different to rebuild master when you have master backup. After the initial installation of SQL Server (or any downtime you can have). Stop SQL Services, copy the system Databases files (.mdf and .ldf) to a save location. If the master gets corrupted. Delete the master mdf and ldf and copy from the earlier saved copy. At this point, if you restart SQL, you will not see any of the Databases, Logins etc that you may have added since copying (not backup) the master mdf and ldf files). Therefore start SQL in single user mode (/m) and then restore the master for last master backup.