Documentation for the SqlBak product is currently under development. We apologize for any inconvenience.
While the documentation is being finalized, you can reach out to us through our support service, and we will strive to respond to your inquiry within a few hours.
Below is a list of articles from our blog where you can find useful materials on using SqlBak:
In addition to the user databases that a SQL Server administrator can create, there are also system databases. The primary ones visible in Object Explorer are master, msdb, model and tempdb. All these databases, except for tempdb, support backup operations. In this article, we’ll discuss whether these databases need to be backed up, and if … Read more
Restoring SQL Server databases from backup files is an important task for database administrators. In this article, we will discuss what backup files are and how to load a BAK file into SQL Server.
BAK files are files created by SQL Server, with the file extension .bak, that contain one or more backups of SQL Server databases. They are designed to restore databases to the state they were in at the time the backup was created.
These files are a physical copy of the data from the database files (.mdf и .ldf) and are not intended to be viewed directly in a text editor.
Importing a BAK file in SQL Server involves restoring a database. You can restore databases from these files using T-SQL commands, graphical utilities such as SQL Server Management Studio or SQLBackupAndFTP, as well as from the command line.
There are several graphical user interface tools available.
SqlBak has an API that allows it to integrate with other applications and services. This article explains how to integrate SqlBak and Zabbix. Sending job results to Zabbix 1. Export the template to Zabbix. It contains items for job results (status, date, backup type). Create a JSON file with the following content: { “zabbix_export”: { … Read more
This article will address the issue of backup encryption, why it is important, and the various approaches available. Why encrypt backups? Data in a database is typically valuable and a target for hackers. However, this data can be accessed not only by connecting directly to the database but also from a backup file. Therefore, protecting … Read more
In this article, various methods of monitoring backups and restores of SQL Server databases will be discussed, including tracking current progress and history. Tracking the status of your initiated backup If you initiate a backup yourself, you can instruct SQL Server to log the progress status by adding the WITH STATS parameter to the BACKUP … Read more
When you perform SQL Server backups on an industrial scale, it is easy to get confused with the created backup files, as the backup itself consists of binary data, making it impossible to understand by simply opening it in a text editor. In this article, we will look at what SQL Server offers to avoid … Read more
This simple guide will help you create backups of SQL Server on Linux.
The only noticeable difference is in the graphical tools.
SSMS is the main tool for SQL Server and is only available on Windows. Connecting from Windows to SQL Server on Linux is not always possible due to port security (1433). You will have to use the command line utility sqlcmd and T-SQL commands.
Log shipping in Microsoft SQL Server is an automated solution for master-slave replication based on the transfer of transaction logs from primary to secondary servers. This process ensures continuous database cloning while minimizing the load on the primary server.
SqlBak enables the execution of SQL scripts and Windows batch scripts within backup or maintenance jobs. By default, script execution is disabled for security reasons. When attempting to add a script to a job, an error message may appear:
Execution of <script type> is prohibited. To allow script execution, please enable the corresponding option in the SqlBak App security settings.
