Microsoft Azure SQL Database is a managed cloud database from Microsoft. It runs on a cloud computing platform, and access to it is provided as a service. If you use SqlBak for managing your database backups and want to backup Microsoft Azure SQL Database as well, here you will find a step-by-step guide on how to do it. Continue reading How to backup and restore Microsoft Azure Cloud SQL Database
If you use Azure Storage to keep your SQLServer backups then you are probably already aware of “Microsoft SQL Server Backup to Microsoft Azure Tool” that allows you to send your backups there. In this post, we will show how it works and why SqlBak does the same thing in a more convenient way.
Usually, database backup files with .bak extension contain data in the standard Microsoft Tape Format (MTF) used by Microsoft itself as well as many backup tools for the Microsoft Windows platform. Many third-party SQL Server backup products including SqlBak and SqlBackupAndFtp produce backups in this format as well.
Files with .sqb extension contain backups in RedGate’s proprietary format. You would need to use some special utilities if you want it to be converted into MTF. Let’s learn more about Microsoft Tape Format (MTF) and SQL Backup format from Red Gate.
If you care about SQL Server performance you need to take SQL Server Statistics into account. Statistics are lightweight and small objects which describe how data in SQL Server tables are distributed. The query optimizer uses them to create query plans that improve query performance. Continue reading How to Update Statistics in SQL Server
The automatic SQL Server health check monitoring must collect crucial metrics to diagnose memory, CPU, I/O issues which are needed for proper SQL Server performance. It also has to have a good set of reliable, accurate configurable alerts which will tell us if the failure occurs. Of course, you can create your own set of scripts and run them every time you need to check the working state of your SQL server. But the easiest way is to use SQL Server health check from SqlBak. It will make all crucial checks for you, collect the statistics and if something goes down will send the email notification immediately. Continue reading SQL Server Health Check
SQL Server health checks and backups often seem secondary to the primary business objectives. And, generally, it is so until your server is down or the data is lost. Only then the true importance of automating these mundane SQL Server maintenance tasks become apparent.
Continue reading Why Do You Need Automatic SQL Server Health Checks?
Any SQL Server DBA worth their salt have their own checklist through which they routinely go to make sure that all systems are up and running. Below we will share with you some crucial points related to SQL Server health check.
Continue reading SQL Server Health Check Checklist
In that post let’s talk about one of the primary section in the daily life for each DBA this is SQL Server backup and restore tutorial. The greatest way to backup and restore your SQL Server database is to apply SqlBak. Using SqlBak you can be sure that your SQL Server database is in safe. Below you can find simple SQL Server backup and restore tutorial. Continue reading SQL Server Backup and Restore Tutorial
Below you can find the solution of the following SQL Server error message:
Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)
Probably you face this error when you try to make SQL Server database backup. It has to be admitted that this error message belongs to the permissions issue on the local disk and user account which is running SQL Server. Continue reading Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)
Working with SQL Server sometimes you have to restore your database and sooner or later during the restoration process you can receive the following error message:
Msg 3117, Level 16, State 1, Line 1 The log or differential backup cannot be restored because no files are ready to roll forward. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally.