HomeSQL ServerHow to take Database Backup in SQL Server 2008 R2?

How to take Database Backup in SQL Server 2008 R2?

It might be important to take the back of the SQL Server database regularly and store them in a secure place which will help you to recover or restore data in case of natural disaster or any other issues.

In this blog post, I will demonstrate a step by step process to backup database in SQL Server 2008 R2.

How to take Database Backup in SQL Server 2008 R2?

Follow the below steps to take the Database Backup in SQL Server 2008 Management Studio R2.

1. Launch SQL Server Management Studio

2. Connect to the SQL Server Instance where the database exists.

3. Expand the Database node and right click the database that you want to backup in the Microsoft SQL Server Database Engine in Object Explorer. This will open a Context Menu. Click Tasks -> Backup option.

4. A Back up Database Dialog box will be opened. Verify the Database Name, Backup type (Full)

5. In the Backup component, select the radio button “Database”. In the Backup set, leave the default name and provide description (optional) and then leave the default value (0) days for backup set will expire after option.

6. Alternatively, you can add the Destination to different path where the SQL Server database back up should be saved to by clicking the “Add” button.

7. Click OK to start the backup process of the SQL Server database. Within some time, you should receive a confirmation message stating that the database was successful if all went fine… The backup file should now be available in the earlier selected path.

    2 Comments

  1. James
    October 2, 2012
    Reply

    What about the transaction logs?

  2. October 2, 2012
    Reply

    try BACKUP LOG …

Leave a Reply

You May Also Like

When dealing with a relational database management system (RDBMS) like SQL Server, compatibility level is an important concept to understand....
In this blog post, let’s learn about the error message “49975 – Unable to load controller client certificate due to...
In this blog post, let’s learn about the error message “49973 – Cannot remove tempdb remote file to local tempdb...