With the second release of the Enterprise version of Time Matters (TM 4) we decided that we needed a formal position on replication. In doing so we determined that our clients deserved to know:  

1. Will the Time Matters database support replication?
2. What are the best practices for implementing replication on a TM database?

As the Lead Engineer for the Enterprise edition it was my responsibility to make the appropriate recommendations for these determinations. After a great deal of research and testing, I developed a subset of tables determined to be safe for replication. A white paper was developed around this list of “safely replicable” tables.

In addition to the white paper, I developed a tool to assist with managing the conflicts involved with replicating the Time Matters Enterprise Database. Unlike Time Matters synchronization, the end user does not have an interface to manage the almost certain conflicts that will arise.

There hasn’t been much update on either of these tools since we updated the white paper for Billing Matters (TM5). With sensitive billing data now needing to be managed from a single location it was determined that several tables should be added to the “do not replicate” list.

A lot has changed since TM5, especially with the addition of new hidden/subtle relationship data, Accounting, General Ledger, Trust Accounting and Accounts Payable. My experience at Time Matters and now in the field has led me to be somewhat concerned with the state of general acceptance and lack of oversight with regard to database replication.

As a community of consultants we need formal guidance and direction from the TM Product group:

1. Does LexisNexis, Time Matters officially support replication?
2. Has a new white paper been developed that can provide the appropriate authority over the proper way to replicate the various editions of the Time Matters database?
3. What are the important issues regarding conflict management?
4. What are the best practices for conflict management (and is the conflict tool sill being updated)?

• < Prev
• Next >