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 …
SQL Server Backup
SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified
Sometimes you may see “SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified” error message when connecting to a SQL Server and don’t know where to start. In most forums people say this is because remote connection is not enabled on the server. This is not exactly correct. Actually, this error message gives customers a very specific information and the solution is quite simple.
POS System Backup Made Easy
A POS system backup is an essential task in any kind of business. Keeping your sales data safe for reporting and auditing is something all businesses should not cut corners in or treat with little importance.
When your company relies solely on an information system (database) to store all of its sales data, then it also must take all precautionary measures to protect this data and periodically make backups of the POS system’s database. We will show you how to do this in the article below.
How to quickly restore a database
If you’re looking for an easy way to quickly restore a database backup then you have found the right place.
Take a look at the article below to find out how you can achieve this.
How to export data from a .bak file to Excel
Were you ever faced with the situation in which you had to extract and export data from a .bak file to Excel (.xls, .xlsx, or .csv format)?
Surely if you have arrived here you are facing this problem and looking for a solution. Well, you have come to the right place. In the article below we will show you how you can achieve this.
SqlBak update: The New Dashboard
SqlBak’s dashboard has been upgraded to be a more user-intuitive interface, in order to provide the most essential information in just a quick glance as well as make modifications to the job.
It’s still very easy to create backups, to schedule them, to set custom backup destinations, and of course, all of the other features you will need to make sure your backup process is up to the highest standard. Let’s have a look!
SQL Server Backup Permissions
Backup permissions: This post will take you through the list of backup permissions a user needs to have in order to be allowed to make the most basic backup operation.
We will also explain what are some of the most advanced options for backing up databases and how you can give these privileges as well to some of your most trusted users.
SQL Server backup report
In this article, you can find a small script that you can use as a small cheat to have access to an on-the-go backup report of your databases.
If you can connect to your database, you can run this query and find out when was the last time your databases were backed up
and when were the last times a Full, Differential, or Transaction Log backup was taken.
But what do you do when you do not have remote access to your databases, but still like to have a quick review of your last successful backups? Well, we’ll cover this too…
SQL Server backup types cheat sheet
SqlBak.com presents you a free SQL Server backup types cheat sheet infographic. This cheat sheet clearly explains the difference between Full Backup, Differential Backup and Transaction Log Backup in SQL Server. Feel free to Download PDF or PNG files.
Backing up database files in offline mode (cold backup)
A cold database backup is when you make a simple copy of the data and log files. For this to work, the database should be taken offline first.
This is the opposite of the hot database backup that is the regular backup performed while the database is in use. In SQL Server it is usually done with the BACKUP DATABASE command.