If you are looking for a tutorial on how to backup SQL database automatically with SSMS just follow the instructions below. Note however that there are better ways to backup SQL Server database than SSMS. This is especially true when you are running MS SQL Server Express that lacks SQL Server Agent – just use SQLBackupAndFTP instead of the method below.
Continue reading How to Backup SQL Database Automatically Using SSMS
SQLBackupAndFTP creates standard *.bak files when it runs locally on the same computer where SQL Server is. For remote SQL Server computer backups SQLBackupAndFTP creates backup script files (*.sql). Whenever possible, you should always opt for *.bak backups against *.sql backup files.
Here we will show you how to backup a SQL Server on the network to the standard *.bak file even when SQLBackupAndFTP runs on a different computer from where the SQL Server is. The main requirement, in this case, is that both SQL server and SQLBackupAndFTP have access to the same shared network folder.
By default SQLBackupAndFTP stores backups in file names like DatabaseNameYYYYMMDDHHMM.zip (eg Pubs201801011120.zip). But you can also use custom file names if you have such needs Continue reading Customize backup file name
SQLBackupAndFTP has an option to backup all non-system databases. This is useful as it would automatically add all the new databases added after the backup job was created. Continue reading How to exclude databases from a backup job in SQLBackupAndFTP