GP2013 - SQL DB Maintenance

(0) Share

Report

Posted on by Community Member

Looking for information regarding SQL maintenance jobs for servers running GP. I backup the entire virtual machine with Veeam, but I also run SQL backup jobs and backup log jobs. While setting that up I saw other maintenance tasks such as reorganize index, rebuild index, and update statistics. Do any of you run any of those jobs?

Only found one post in these forums related to the issue, sorry if I'm not searching with the right terms.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Jonathan Fear on at

Like (0)

Report

Are you asking if you should run these or what these jobs do?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Asking if those three jobs should be run? Sometimes maintenance like rebuilding or reorganizing an indexes should only be done if a db is below a certain threshold (20% fragmented for example).

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

There isn't a hard number on when these should be ran. I would refer you to the following KB:

875193 Information about database maintenance plans for Microsoft Dynamics GP or for Microsoft Dynamics SL on SQL Server 2008, on SQL Server 2005, or on SQL Server 2000

mbs.microsoft.com/.../KBDisplay.aspx;EN-US;875193

Otherwise you could check out the Performance White Paper which discusses this as well.

mbs.microsoft.com/.../MDGP2010_WhitePaper_Performance

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for your help. Both mention the maintenance commands I've talked about above, but stay away from specific guidelines on how often, given general database sizes. I understand why they may do this, but I'm just frustrated because I'd I don't have much precedence to follow.

Was this reply helpful? Yes No
Verified answer

Jonathan Fear on at

Like (0)

Report

Again that is because there isn't a hard number. Some people do it one a month others every few months. There is no reason to do this unless you are experiencing performance issues. If we recommended it once a month maybe that works for you but not every else. It is impossible to have recommendations like this when each company would be different.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks

Was this reply helpful? Yes No
Suggested answer

Victoria Yudin 22,769 on at

Like (0)

Report

For what it's worth, we typically set up general maintenance (like check DB integrity and reorganize index, update statistics) to be a weekly job. Obviously different environments might require different settings, but for many installations I think that is a good guideline.

Was this reply helpful? Yes No