Open Forum

Like what you see? Discover the benefits of the GPUG Community. Learn More

Check Links Long Duration Recommendations

  • 1.  Check Links Long Duration Recommendations

    Posted 6 days ago
    Hi, all. I'm trying to get through Check Links & Reconcile for the first time in our environment and I'm running into issues with the time it takes for certain series to complete. For instance, In our lab environment, I was running CL for Purchasing History and it ran well over 40 hours. I've used CDA to archive as much data as the Finance team will allow and I've done index and stats maintenance.

    I was wondering if anyone had recommendations to speed up CL & Reconcile and, I'd love to hear how you may have encouraged your company to allow enough downtime to complete the processes.

    Thanks.

    ------------------------------
    Jon Godwin
    Database Administrator
    Boulder CO
    ------------------------------


  • 2.  RE: Check Links Long Duration Recommendations

    Posted 6 days ago
    Edited by Jon Godwin 6 days ago
    If it matters at all, I've got a 290 GB company database with 115 GB free from CDA.

    ------------------------------
    Jon Godwin
    Database Administrator
    Boulder CO
    ------------------------------



  • 3.  RE: Check Links Long Duration Recommendations

    TOP CONTRIBUTOR
    Posted 5 days ago
    ​Was the 40 hours on one company or to complete for all companies?  If it was for all 290 companies, I'd actually say that's pretty good.  If just one, not good at all.

    I like to run Checklinks in my test environment (using a copy of production) so I can then go in and fix the issues it finds in the live environment (where possible).  I will admit that running checklinks can take a long time to complete because of its thoroughness and I don't have any suggestions for speeding it up.  I run a complete checklinks (all modules, all companies) as part of an upgrade (which I'm planning right now).  Just on our 11 companies (not nearly as many or as voluminous a data set as what you have), it takes about 30 hours to complete that task.

    As to the necessity and finding the downtime, you have to make the case to your finance time to take a planned day off or risk having to take two unplanned days off if you run into a big problem.  It's all risk-reward.  Are you a 24x7x365 shop or can you do this on a weekend where demand isn't so high?

    ------------------------------
    Blair Christensen
    Database Administrator
    Oppenheimer Companies, Inc.
    Boise ID
    ------------------------------



  • 4.  RE: Check Links Long Duration Recommendations

    Posted 5 days ago
    Thanks for the feedback, Blair. I think I may have misspoken. We have one company with a 290 GB company database. It's taking 40 hours for the one company and just for Purchasing History. To be honest, I'm not sure how long it would take to complete, because I killed it and started fresh thinking there may be a problem in my LAB environment.

    We have some integrations that are using GP 24/7 but I can get about 5 hours per night and 10 hours a day on the weekends if I push. That's why I'm concerned about getting through this process in pieces and to get each series to complete as quickly as I can.

    I like your idea of convincing finance of the risk-reward factor of getting through CL.

    ------------------------------
    Jon Godwin
    Database Administrator
    Boulder CO
    ------------------------------



  • 5.  RE: Check Links Long Duration Recommendations

    TOP CONTRIBUTOR
    Posted 4 days ago
    So, I read the thread a little more carefully and picked up on a few hints. You said this is the first time you're running Checklinks AND you said you're running it on Purchasing History.

    With that size of database, if you've been on GP for a really long time, that's going to be a LOT of transactions to process.

    That said, I've never seen much use in running Checklinks on history tables unless there's a known issue you're trying to solve. Or as a preparation for upgrading.

    Try running the Checklinks just for the Work files and see how long that takes. The Work files are the ones that have a greater chance of getting corrupted.

    The Sales work tables seem to process relatively quickly on more current GP Versions but the Purchasing work tables do seem to take a longer time to Checklink.

    David

    ------------------------------
    David Flowers
    System Admin -GP and Salesforce Support
    RMG Enterprise Solutions
    Addison TX
    ------------------------------



  • 6.  RE: Check Links Long Duration Recommendations

    Posted 4 days ago
    Thanks, David. As we're not getting ready for an immediate upgrade, I will try just running it on work tables and see what kind of times I can get. Do you know if I run reconcile immediately after, if not running CL on the history tables will have a negative impact?

    ------------------------------
    Jon Godwin
    Database Administrator
    Boulder CO
    ------------------------------



  • 7.  RE: Check Links Long Duration Recommendations

    TOP CONTRIBUTOR
    Posted 11 hours ago
    You do not necessarily need to run check links on a regular basis.  Last time we did a version upgrade I wanted to persuade  Great Plains support to recommend that we run check links on all our databases, and they declined no matter how much I twisted their arms, they said that perhaps we should run the check links on A/P and A/R transactions to rebuild the keys files.

    In particular, for our company, after testing, we decided that (IMHO of course) we should NEVER run the check links for the POP files.  The POP check link routines ONLY reconcile the purchase order files, they do not correct any errors in the PO10500/10600 link files, which means data inconsistencies in the POP receivings/invoice that tie to the GL are not repaired.  Part of the problem is I think the check links routines for the POP module were probably rushed, veterans will recall that Great Plains had great problems finishing the POP/SOP modules, they were probably over-ambitious in their pseudo-object oriented dexterity enhancements.

    ------------------------------
    Bruce Strom
    Programmer Analyst
    Associated Grocers of Florida / Supervalu
    Sunrise FL
    ------------------------------