Microsoft SQL Server supports four different types of backup

Microsoft SQL Server supports four different types of backup. You should choose the
type of backup you will be using carefully in order to ensure that you get the level of
security you require.


The four types of backup are:
· Database backup – this makes a backup of the entire database.
· Transaction log backup – this makes a backup of the entire transaction log.
· Differential backup – this makes a backup of all committed entries since the last
database backup.
· File and filegroup backup – this makes a backup of individual files or filegroups
within a database.

These can be combined to form many different types of backup and restore
procedures. This allows you to design a backup and restore strategy that fits your
database needs.

You can also use the Navision client based backup/restore tool when you are running
on the SQL Server Option. However, the SQL Server backup/restore system is
server-based and is therefore considerably faster than the Navision backup/restore
tool, which is client-based.

It is possible to restore a SQL Server backup of a Navision database directly into SQL Server without using Navision. You can also create a database directly in SQL Server without first having to create it in Navision and then restore a SQL Server backup of a Navision database directly into the database on SQL Server.
SQL Server allows you to make backups when the system is in use. With SQL Server,
you can also automate many of your administrative tasks, including making backups.
SQL Server allows you to establish a database maintenance plan (with the help of a
wizard) that includes database optimization, integrity tests and a backup plan.
One of the great advantages that SQL Server has over Navision Database Server is
its ability to record a transaction log. Transaction logs give SQL Server a roll forward capability that you can use to recover all the committed transactions that were carried out up to the point of failure. Roll forward is achieved by restoring your last database backup and applying all subsequent transaction log backups to recreate these transactions.