Backup Compression is a feature of SQL Server versions 2008 and later (2008, 2008 R2, 2012) which offers you more benefits without any cost to your data or its integrity.
In spite of \having been through a data compression process, the compressed backup actually has a few advantages over regular backups.
Unfortunately, there is no standard or specific feature to backup a table in SQL Server, but there are workarounds.
This can be a very common request from clients, as they might want to backup specific tables from their databases, and as there is no feature in SQL Server that offers this functionality out of the box, then we need to create our own way.
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?
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. The result of this is all the data is wiped off.