Share
Report
620Background: We are creating a "history" company. To create the company we have taken a copy of the active company and restored it over the newly created company. The next step has been to remove all history that we do not want to keep in this new company. The process has been extremely, painfully SLOW. I started looking at some of the stored procedures used to do the history removal, which led to looking more closely at the underlying database tables and the respective indexes.
What I noticed is that along with some "missing" indexes, indexes that based on the where clauses should be added to expediate the removal, many of the tables do not have a clustered index. SQL Server in general has always indicated that performance will be better if a table has a clustered index.
Does anyone have experience in analyzing and adding clustered indexes to MS Dynamics GP tables? Is there a white paper addressing this issue? Normally I do not like to add custom indexes to an ERP but it seems that performance in Great Plains would benefit from the addition of clustered indexes.
Any thoughts or experience that can be shared?
Thank you in advance for your comments & ideas.
*This post is locked for comments
All responses (
Answers (
