It doesn’t matter if a company is large or small, almost every database administrator needs to maintain a copy of the production databases in a test environment for testing and development needs.
All you need to do for this is to copy the databases from the production server to a test server, and this can be done in different ways. Let’s take a look at them. Continue reading How to clone SQL SERVER database to a Test Environment
Maintenance of your databases is as important as regular backups. Once scheduled backups are set, the thought may appear that your data is safe and sound and it is, until a problem appears.
As a rule, databases don’t crash completely, but there may be a sharp decrease in performance because of server laсk of disk space or any other issues that can corrupt databases. That’s why it’s highly recommended not only to perform regular backups of your databases but also maintain them. Continue reading How to automate maintenance of your databases
Amazon RDS SQL Server is a cloud database from Amazon, one of its differences from classic SQL Server is the way it performs backups. RDS SQL Server does not support the T-SQL BACKUP DATABASE construction but instead offers several other approaches such as restore point-in-time, snapshots, native backup to S3, and Export Data-tier Application.
Here are ways to perform a backup and restore:
Continue reading How to backup and restore Amazon RDS SQL Server
Log Shipping is SQL Server technology that is available in both the Standard and Enterprise editions. The technology may be useful in solving the following problems:
Continue reading Scheduled Restore. How to Set Up Log Shipping
If you get the following error message during a backup:
[JOB-BAK:1301#1] Failed to backup <database name> database with "Full" backup type: Failed to backup <database name> database. There is no destination selected to keep Full database backup type. Continue reading [JOB-BAK:1301#1] Failed to backupdatabase. There is no destination selected to keep Full database backup type
If the following error message happens:
[DST-1:1003#53] Destination error: Failed to open "\\networkpath\backupfolder" destination connection. > The network path was not found
Continue reading [DST-1:1003#53] The network path was not found
Typically, the following error message:
Destination error: Could not find a part of the path 'y:\1'. Trying again... Destination error: #[DST-1:1001#103] Failed to connect to the Folder destination. > Failed to create folder "y:\1". > Could not find a part of the path 'y:\1'.
Continue reading [DST-1:1001#103] Destination error: Could not find a part of the path
During the backup you can face the following warning:
[Warning] [JOB-BAK:2006#11008]. The previous full backup of <database name> database was created with a different application (non-SQLBackupAndFTP). You may not able to restore the database automatically using SQLBackupAndFTP.
If, after installing PostgreSQL, you face “psql not recognized as an internal or external command” error when you try to run psql from the command prompt, then most probably all you need to do to solve this problem is to add Postgres’s bin directory to the PATH system variable (the PATH is a system variable which allows Windows with the help of the Command prompt or the Terminal window find executables).
In this blog post, we’ll share seven simple steps that describe how to add the folder to the Windows 10 PATH variable.
How do you make your PostgreSQL database backups, with the help of pg_dump utility or in any other way? Do you prefer to store your backup in the cloud, like Amazon S3? How much time do you usually spend every day to make your database backup and send them to Amazon S3? It is really very easy to backup PostgreSQL to Amazon S3 with the help of SQLBackupAndFTP. You can create a backup job just in a few minutes. Continue reading How to Backup PostgreSQL to Amazon S3