Many SQL Server DBAs are from time to time confronted with a disaster caused by unintentional or malicious changes on their database. Whatever the nature or intention of these changes are, they can cause great issues whether it was the data loss or a structure loss. With this in mind, it is important to start with the recovery process as soon as possible. Having a recovery scenario and solution for these situations prepared is also a great benefit, and is generally advised where possible. Whatever enhances our chance to recover in case of a disaster, and increases chances of successful and full recovery should be taken without any second thoughts. In this blog post we will learn about Database Disaster Recovery Process.
I have blogged before regarding how to Identify Application vs Network Performance Issues using SQL Server Dynamic Management Views (DMV). You do have some further diagnostics as well as optimizations you can perform to drill down into the network issue and address it.
Interviews are two way streets, sometime interviewer asks questions and sometime candidate asks questions. In a recent interview, I was asked by a candidate “How to Get Started with SQL Server 2016?”. I think it is a very good question. Let us discuss that today.
One of the most common question I get on blog is – how do I attach database without log file. I have previously blogged about it over here. I request you to read this blog post if you want a solution where you can learn how to attach database to SQL Server with the help of T-SQL.