SqlBak.com presents you a free SQL Server Formatting Types Cheat Sheet. We spent several hours composing it for you.
We would like to tell you about a brand new SqlBak feature that allows users to store backup files in a different place if the main destination fails.
When you delete, update or insert the data, the SQL Server Database Engine updates the indexes automatically. Over time such changes lead to the data in the index being scattered all over the database, in other words – fragmented.
Now with the help of SqlBak, you can manage backup jobs and maintenance jobs with your team members separately or even with an entire team. That has become possible due to a brand new “Users” feature available on the “My Account” page. This option can be useful when you need to add one or more users with Read-Only or Manager privileges to your account.
The DBCC SHRINKDATABASE is used when it is necessary to shrink the size of the log and data files in a particular database.
Now you can run regular SQL Server maintenance jobs with the help of SqlBak. This feature can be useful if you regularly need to make some changes to your database. All these changes can be made by adding any SQL Server command (using T-SQL) or adding Windows batch (*.cmd, *.bat).
Amazon Web Services (AWS) offers a large, sometimes bewildering array of server, storage, networking, and analytics cloud offerings, as seen here. One of their storage products is Amazon Glacier, in addition to the older storage solutions – S3 and Elastic Block Store (EBS). Glacier is a very affordable solution intended as a write-once, retrieve-seldom storage medium for long-term storage. Think of it as a storage locker that’s far away from your home, as opposed to your at-home garage or cabinet locker. It is also a good choice for your SQL Server backups …
When backing up your SQL Server database, you have the option of taking transaction log backups. These are quick, small backups containing a sequence of all your database’s changes. Transaction log backups are mightily useful for point-in-time recovery.
It goes without saying that as a DBA, one of your most important tasks is to schedule and ensure regular backups of your databases. But by ‘databases’ here, we usually mean your user-created databases. But SQL Server also automatically creates and maintains a number of system databases. So should you also back these up? Well, the answer isn’t a simple yes or no …
As a DBA, you have almost certainly taken a backup from one server for the purposes of restoration on another server. It’s a somewhat tedious and manual process, but most of us are sort of resigned to it and accept it simply as a necessary evil of the DBA role. I mean, it’s not like you can automate the entire process, right? Well, hold that thought …