Sql server db maintenance plan for nav db

(0) Share

Report

Posted on by mbr

5,136

Hello,

i plan to create a db maintenamce plan for the nav 2013 db in sql server 2012. The main objective is to create a daily backup of the db. I plan to also do some maintenance by allowing sql server to improve statistics and finetune indices. Also since we are using simple recovery mode, i plan to shrink transaction log. Do you have any advice? Suggestions? Best practices?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

Saurabh Shah 4,560 on at

Like (0)

Report

Hi,

Please follow below links for SQL DB maintenance plans details for your reference to cross check your steps.

msdn.microsoft.com/.../ms187658(v=sql.110).aspx

msdn.microsoft.com/.../hh710041(v=sql.110).aspx

msdn.microsoft.com/.../ms189953(v=sql.110).aspx

Apart from this, please make sure that you follow the separate disk drive to take backup of SQL database.

If you want to take the backup on daily basis then it is just suggestion to incremental backup daily and full backup every week.

Keep one copy out of the system atleast on daily basis. Take backup on non working time.

Regards,

Saurabh Shah

Was this reply helpful? Yes No
Verified answer

keoma 32,729 on at

Like (0)

Report

hi,

the backup drive should be a different drive than the one the sql server is installed.

be sure that at least a weekly backup is stored to an external storage (because of complete power off, fire, ...).

check if there is a USV to save the hardware, where the sql server is installed.

best regards

Was this reply helpful? Yes No
mbr 5,136 on at

Like (0)

Report

thank you much! I got the db maintenance plan working! I thought there were other things to consider since it's a Nav DB. But it's just a sql server db and should be treated as such.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

For anybody who runs across this post:

It should be pointed out that the Full Recovery model should be used for "mission critical" databases (for example, if you could get fired for losing data or if the company might risk having to close business if they lose data, then the Full Recovery model should be used). The transaction log is not saved during Simple Recovery model, so there is an increased risk of data loss.

With the full recovery model, everything is logged, so there is a lower risk of data loss. It is recommended to backup to a file share and then backup the file share to tape. Keep in mind that data can be lost when switching Recovery Models and of course some recovery models are not appropriate for a production environment.

On a different forum, someone pointed out that if you are willing to lose a day or week of data, then you could use the Simple Recovery model and take daily or weekly backups. If you can only tolerate losing an hour of data (for example) then you should use Full Recovery backups and take an hourly transaction log backup.

Was this reply helpful? Yes No