Backing up your SQL Server databases is the only way to protect you from potentially catastrophic data loss.
Place your database backups on a separate physical location or device from the database files. Thus, you won’t lose your data and SQL backups at the same time.
To avoid transaction log management and simplify backup and restore, use the simple recovery model. To minimize work-loss exposure, at the cost of administrative overhead, use the full recovery model.
Schedule regular backups as part of a database maintenance plan. If there is a predictable off-peak period, you can schedule full database backups for that period.
You do not have a restore strategy until you have tested your backups. You must test every type of backup that you intend to use by restoring it onto a test system.
A tool used for configuring, managing, and administering all components within Microsoft SQL Server.
Microsoft's and Sybase's proprietary extension to the SQL (Structured Query Language) used to interact with relational databases.
A task automation and configuration management framework, consisting of a command-line shell and the associated scripting language.
Unlimited Servers & PCs