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.
Recovering lost data that was deleted or truncated can be fairly quick and easy, depending on the environment in which the database resides, recovery measures implemented before and after the data loss has occurred, and the tools used for the job. In this blog post we will learn about how to recover truncated or deleted data when a database is (or not) available.
Just the other day I was busy during a performance tuning exercise I explained to the team of DBA that how much log file is critical and important for their performance. Once I was explaining the importance and role of the LDF file in the performance, one of the DBA from the team asked me question about what would they do if they somehow lose the LDF file or just have corrupted log file which they do not care now. Well, I though it was a very important question and I believe it can be a very good interview question as well. Let us learn about how to attach the MDF data file without LDF log file.
The other day, I received an email from a user, who had dropped master database in their system. I told him directly that he should have not dropped master database as that is a very important system database. It is really strange that after so many years quite a few of the people do not know what is a master database in SQL Server.
Few days back I wrote blog about SQL Server 2016 Developer Edition free download. If you didn’t get a chance to have a look, here is the link: Download SQL SERVER 2016 Developer Version for FREE. Let us learn about how to install Sample Database WideWorldImports.
ApexSQL Backup is a powerful yet simple tool for Microsoft SQL Server which represents a fully equipped command center for database backup and restore jobs management. It enables users to create and schedule backup related jobs (backup, restore, log shipping, index defragmentation…) and monitor all scheduled backup activities or overview complete backup history on multiple servers across the domain.
ApexSQL Backup is designed to create and work with native Microsoft SQL Server backups and databases, and supports all backup options which can be used in the SQL Server Management Studio and encompasses them in a simple and user friendly UI which revolves around simple wizards for each particular job.
This seems to be the third week that I am writing about ReadOnly databases, this blog is in continuation of last weeks notes. When I wrote the notes from last week, one of my blog reader said if it is possible to get the ReadOnly error without making the database into a ReadOnly database. This got me thinking and I couldn’t sleep that day. And a quick call to my friend to get some ideas – the answer was simple – using Snapshots.