x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 57 subscribers
  • Views 2042 views
  • Users 0 members are here
Browse Forums
Sage Timeslips Anywhere Announcements
6
topics
1
replies
Sage Timeslips Anywhere General Discussion
13
topics
13
replies
Sage Timeslips Premium Announcements
57
topics
17
replies
Sage Timeslips Premium General Discussion
2k
topics
8k
replies
bgerstel

Complexity of Data Verification process?

SUGGESTED
Posted By

My office is about to implement a long-needed upgrade from Timeslips 2004 to the current version. We have a consultant coming in next week to do the "step-by-step" process that I know is required when upgrading from such an old version. But my boss wants to maximize the time she spends on training and such, and let me do as much of the nitty-gritty technical stuff as I can.

I ran a Data Verification on our database (without and error-fixing or re-indexing turned on), and it came up with a grand total of one error message, as follows:

Checking Integrity Audit Table

---ERROR---

The Paradox table appears corrupted.

BTree record number mismatch from block (1) record(16) to block (17)

Table Error Total: 1

Assuming I take proper precautions (back up the database beforehand, keep everyone off Timeslips while I'm working, etc.) how likely is it that I can just run the Data Verification with the error-fixing turned on, and fix the problem, given that I'm just a reasonably smart generalist techie, rather than a Timeslips specialist?

And if we let the professional do the work, approximately how long should we expect it to take?

Thanks in advance.

  • 0

    Here is how I would try to fix this error. Create a new empty database. Exit Timeslips. Copy the real database to the local workstation.  Copy the audit.* tables from the empty database into the copy of the real database, replacing the existing files. Run data verification, rebuild index files on the local copy. If no errors found you can move the copy back to the server and begin using this as your real database.

    Please note, these instructions are for this particular error in this table, do not interpret this as a recommendation to use these instructions for other integrity errors.

  • 0
    SUGGESTED

    bgerstel:

    First off, kudos to you for thinking ahead and seeking to maximize your investment in a consultant's time.  Too few folks do that.  So you are already ahead of the pack there.

    Secondly, nice job on running the Data Verification with only the Look for Errors option checked in anticipation of the upgrade.  Any consultant would also do that before upgrading, and your identifying the problem early is good.  

    Thirdly, I'd probably lean towards letting the consultant fix this one when they come in since they will already be onsite.  The key for me is where the error is.  It is in the Audit table.  Two things about that table.  1) Most firms could care less about the data in that table and 2) it is often one of the largest tables in the database.  So it takes up some space not only in the actual database but also in all backups.

    IF (and yes, that is a big IF) your firm does not care about this data, your consultant could just empty out the tables and then convert, giving you a slimmer, leaner upgraded database.  It should not take much additional time at all and would be my recommended course of action.

    Hope this helps.  

    If you think this suggestion was especially helpful, please consider rating it within the five star option, or clicking the green Yes button next to the "Did this answer your question?" option below.  Thanks.

    Nancy Duhon, Esq.

    Master Certified Consultant for Timeslips,

    Certified Consultant for Amicus Attorney and Credenza

    Duhon Technology Solutions, LLC

    a member of Certified Resources Network, LLC

    [email protected]

    404-325-9779

    Providing personalized local and remote online support for Timeslips users for over 19 years. Available for private consultations, including older/unsupported versions.

*Community Hub is the new name for Sage City