“How much time SQL Server is going to take to complete the database Backup or Restore” – This is one of the very common questions DBAs face in day to day life when they are performing database refresh activity, database migration activity, or any adhoc activity where DBA may want to have a DB backup before the activity takes place.
Data is one of the most valuable assets of any company. To ensure you keep your data safe, database backups are essential.
After the release of NAV 2013 R2, Microsoft discontinued the NAV Database backup (.fbk) feature. An additional option was added to allow for import/export of data in NAV 2013 R2, but doing a backup using the Import/Export Data feature is time consuming.
Today my customer Thomas Ditlev from ACO Nordic asked me to bring a backup of the data in a database to a colleague, nothing new about that.
I totally lost my cool, when he started the backup functionality inside Dynamics NAV, exported the data and saved it on my USB drive.
Several weeks before our customer’s go-live of Microsoft Dynamics NAV 2015, users were vigorously testing NAV as we were ironing out the specifics of the customer’s desired configurations. During this process, we wanted to start with a clean testing environment (where we wanted to use the exact configurations of the production environment and there weren’t any posted transactions obfuscating our testing scenarios).
The ability to backup and restore a company has been added back into NAV 2015. This capability was lost when 2013 was released and the “Classic Client” was discontinued. Losing this capability made it more difficult to make a copy of a company in order to create a test company based on the current live data.