Database Rework

[escott]

I inherited a client with a database first implemented in 2006 and which is currently hosted by a FM hosting service on a shared FMS14 machine.  The client is in a remote location with poor connectivity and is having me implement MIrrorsync so he can work offline without the incessant delays he currently suffers.  Once that works, he would like to move on to some enhancements and fixes in the database.

The naming conventions in the database are bad, and do little to shed light on form or function.  Once Mirrorsync is implemented, how much latitude will I have with respect to renaming things, and what would the recommended process for doing so be?  

[Ocean West]

If you rename things you need to make sure the fields are on the sync layout - and then you need to request the new script steps again - or re run the config - to make sure all your changes didn't mess up the Sync - also too if you are using SQL for any queries. 

I wouldn't rename things while there is an un synced client out in the wild - would wait till all devices are idle. do the major work issue a new build to all remote users. (clean clone)

 

 

also, depending on the user's geographical location may consider hosting on a provider closer to them as it may be less latency. 

[escott]

2 hours ago, Ocean West said:

If you rename things you need to make sure the fields are on the sync layout - and then you need to request the new script steps again - or re run the config - to make sure all your changes didn't mess up the Sync - also too if you are using SQL for any queries. 

I wouldn't rename things while there is an un synced client out in the wild - would wait till all devices are idle. do the major work issue a new build to all remote users. (clean clone)

 

 

also, depending on the user's geographical location may consider hosting on a provider closer to them as it may be less latency. 

Thanks for the things to consider, Ocean!

Fortunately there is only one remote user and the poor link is the last mile link to him in Newfoundland - no option for re-hosting.  Renaming existing fields should be OK, I'm assuming, since they will already be on the sync layout and re-doing the scripts should then pick them up.  Adding fields would require placing them on the sync layouts (I'm deducing) and then re-doing the scripts.  The database has no SQL queries so I should be OK there.  I can work on the database on the weekends or evenings when the remote user is idle.

Your sharing is much appreciated!

[Ocean West]

With the latest version of MirrorSync you can use JDBC and restrict records that sync by using SQL so if the underlying fields are renamed that portion would break.