Skip to main content

Database Backup from SQL Server Managment Studio


Hi all,

Some Client requires to take database backup on daily basis but due to increasing size of data its is tedious and time consuming if we suggest to go for Navision Backup.At this point the best solution to suggest is to take backup from SQL Server.So lets discuss how to take backup of a database from SQL Server Managment Studio.

For taking Backup from SQL Server there are certain steps -



 Open SQL Server Management Studio on Server where the database resides.












Login to SQL Server Management Studio and Drill Down to the Database whose backup you want to take and Right Click It. Now select option of Backup.












The Next Windows shows you the details about the database and you can select the Destination path and file name here.
















You can change the path and file name of the backup by first clicking on Remove which will remove the existing (default) path and file name and then Add.. to set the new path and new file name for backup.
















Remember that file name should end with .bak Extension.
Then Click Ok and the backup will be done on the destination Location.
















Thanks & Regards,
Saurav Dhyani
http://saurav-nav.blogspot.com/ 

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.