I noticed a pinned thread on the Time Matters forum regarding SQL Express backup. Here's an extremely simple yet effective process I suggest to clients using SQL Express. 

All flavors of SQL Server, including SQL Express, ship with a utility program that will execute SQL script from the Windows command line. This allows sites running SQL Express a very simple, cost-free opportunity to perform automated backups.

sqlcmd -S .\sqlexpress -Q "exec timematters9.tm9user.tm_backup timematters9, 'auto'" -o sqlbackuplog.txt

This command can be executed in an automated task. The result will be the same as running the backup from inside Time Matters. If you have not modified your TM backup procedure, a backup will be created in the default SQL Server backup folder with the name of the current day of the week.

WHERE
.\sqlexpress = the name of the Sql Server Instance
timematters9 = name of desired database to be backed up
tm9user = name of the time matters database owner

Just add this command to the Windows scheduler and you will have a simple to implement, centrally managed automation system for performing backups and any other SQL server maintenance you would like to perform at a regular interval.

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)?