Having the possibility to backup your SQL Server databases to Windows’s cloud platform is very convenient, easy, and takes a great weight off your organization’s shoulders but there are a few things that improve this process.
Just by adopting a few good practices in your work with Azure, you can improve the entire flow of backing up and restoring your databases.
There is good news for SQL Server DBAs and also for other users who are interested in backing up their data to safe and reliable cloud storage.
Microsoft has announced a couple of days ago several new ways of backing up and recovering SQL Server databases to their online cloud-based storage platform and infrastructure system, Windows Azure.
Have you ever tried to restore your database, but while doing so the operation is stuck in RESTORING state?
If the following steps are similar to what you did, then you can find the answer at the end of this article:
In order to understand the importance of SQL Server backup and restore, imagine a situation in which one of your colleagues creates a SQL statement without a WHERE clause and executes it, resulting in all of the data being destroyed.
If your SQL Server transaction log (LDF) file is too big – you are doing something wrong. As technet puts it:
Typically, truncation occurs automatically under the simple recovery model when database is backed up and under the full recovery model when the transaction log is backed up. However, truncation can be delayed by a number of factors. For more information, see Factors That Can Delay Log Truncation.
